Add patch for config route about map-config-api HOT 7 CLOSED

Hi @kothariroshni8 yes so the way this is working is that we, for example, want to save a custom theme for an organization:

{
  "name": "custom-theme",
  "data": "{ data for the custom theme }",
  "ref_id": "xxx",
  "ref_uuid": "xxx"
}

Either the ref_id or the ref_uuid is to link the organization (not entirely sure which one anymore 🙃)
When the user updates the theme for the organization we only update the data part, so I think we should use a patch

So the body of the request will just contain the data
I hope I explained it, if you have more questions feel free to just ask

from map-config-api.

I would like to work on this issue.

from map-config-api.

@kothariroshni8 yes please go ahead!

from map-config-api.

Hi @RubenSmn I was stuck at some other work. starting this now. I have some doubts

1. will it be patch or put end point?
2. if it is patch then can you share sample request body ? as i understand we have only one data column in database.

from map-config-api.

Hi @RubenSmn ,
as i see sample data both ref_id and ref_uuid can be null
{ "id": "7d79fba9-2624-4232-ae19-049deac1f30f", "name": "featured-planter", "data": { "planters": [ 940 ] }, "ref_id": null, "ref_uuid": null, "created_at": "2022-08-30T10:15:54.320Z", "updated_at": "2022-08-30T10:15:54.320Z" }
should we do it based on "id" column, it will be unique identifier?

from map-config-api.

Yes I think that is fine

from map-config-api.

Fixed by #30

from map-config-api.