Closed EPajares closed 1 year ago
@cinaaaa Could you add a view for this in the dashboard?
@EPajares Could please clarify that what you mean by adding a view of this to the dashboard? you mean mock up or...?
I actually mean adding a new view like for the other settings. So making use of the mockup endpoints.
I actually mean adding a new view like for the other settings.
Ok, then If I can connect it to a mock API then it's not possible to ship it to the production, is it OK?
Yes. You can keep it in a feature branch
Hey @EPajares, This is the realistic view in the dashboard, much like the layer styles view.
GET /api/customiztion-tables -> list of the record with a unique ID
PUT /api/customiztion-tables/{id} -> { type: "test", test:{value: null} }
POST /api/customiztion-tables/{id} -> { type: "test", test:{value: null} }
We already have some endpoints for the customizations; however, here, the settings for the specific user customization are manipulated. In this case, the Base-settings are changed.
So I would propose to add the endpoints in this section and use the following path: /api/customization/base
. The settings and the structure are pretty sensitive, so we should validate the input and allow only the superusers to use the endpoint.
I think we should not allow a POST endpoint as this would make the input hard to validate. Furthermore, the settings here are very rarely changing. Therefore it would be fine to only have GET and PUT.
Goal of this issue
We have the table "customer.customization"
We do have some settings here as JSON. We need a dummy endpoint to have something working for the dashboard.
Resources
Deliverables
Branch to derive