[Layout] Does renaming collection will erase collection's layout configuration

Justin_Martin · July 5, 2022, 1:47pm

Hello,

We have a collection name “lead” and we would like to rename her “lead-family” (in code). We were
wonderring if this operation will remove all of layout configuration (field, altered value, …).

If it’s the case, can we copy the layout configuration in our new collection ?

morganperre · July 5, 2022, 4:13pm

Hello @Justin_Martin,

Unfortunately, it will erase the layout configuration for this collection.

To understand and help us get better in the future, why do you need to change it code-wise?

Impossible to do that too. I’m gonna push your request to the product team.

Kind regards,
Morgan

Justin_Martin · July 6, 2022, 2:22pm

My problem is due to a missing of renaming the collection when I splited “lead” into “lead-family” and “lead-institution”. I also want to rename my model but due to the declaration of collection it’s not easy without renaming collection.

The second cause is link to the declaration of collection :
collection('collection-name-and-model-name', { .... })

We can’t define the model to use in collection declaration, the collection and model must have the same name. If we break this rule, the front will request the wrong endpoint because the default route are generated by Resources for each model and not each collection.

github.com

ForestAdmin/forest-express/blob/main/src/routes/resources.js

const { inject } = require('@forestadmin/context');
const auth = require('../services/auth');
const path = require('../services/path');
const ResourceSerializer = require('../serializers/resource');
const ResourceDeserializer = require('../deserializers/resource');
const CSVExporter = require('../services/csv-exporter');
const ParamsFieldsDeserializer = require('../deserializers/params-fields');
const PermissionMiddlewareCreator = require('../middlewares/permissions');
const RecordsGetter = require('../services/exposed/records-getter.js');

module.exports = function Resources(app, model, { configStore } = inject()) {
  const { Implementation, integrator, lianaOptions } = configStore;
  const modelName = Implementation.getModelName(model);

  this.list = (request, response, next) => {
    const params = request.query;
    const fieldsPerModel = new ParamsFieldsDeserializer(params.fields).perform();

    return new Implementation.ResourcesGetter(model, lianaOptions, params, request.user)
      .perform()

This file has been truncated. show original

Proposal :
An other definition of collection with a new “model” params can allow us to link a model and a collection :
collection('collection-name', 'model-name' { .... })
and change the reference modelsManager.getModelByName(name) by modelsManager.getModelByName(modelName)

morganperre · July 7, 2022, 12:32pm

Hello @Justin_Martin,

Thanks for your proposal. In this case, the second parameter is like a fixedModelName.
We can study this solution, but we should look at potential drawbacks…

We don’t have the bandwidth to work on this right now.

I have shared your feedback with our product team so they can prioritize this in the future.

Kind regards,
Morgan

Topic		Replies	Views
UI Layout and Collection Configurations reset to Default in Forest Admin Help me!	2	8	December 18, 2024
Layout editor: missing reorder/show/hide button on "create" Feature suggestions dashboard	4	180	November 15, 2023
Loss collection configuration Help me!	3	120	January 25, 2024
Layout refresh problem Help me!	20	837	February 3, 2021
Copy one collection layout to another team Feature suggestions	2	616	October 29, 2020

[Layout] Does renaming collection will erase collection's layout configuration

Related topics