- Issue created by @effulgentsia
- 🇮🇳India soaratul
What exact change we need to do in the UI for 👇?
When conflict IDs exist, these will be marked up differently in the pending changes UI
Create an api slice, publishAllPendingChanges that posts to the controller added in
📌
Create an endpoint to publish all auto-saved entities
Active
.
Create a slice or extend an existing one to keep track of 'conflict ids'
The mutation can return a 409 when conflicts exist. In this case it will return the list of conflicted IDs and the new auto-save data. Use a manual cache update in the mutation to update the pending changes query data AND the conflict IDs
When conflict IDs exist, these will be marked up differently in the pending changes UI
The mutation will return a 200 on success, this should prompt the client to empty the pending changes and conflict IDs
Postponed
0.0
Page builder
What exact change we need to do in the UI for 👇?
When conflict IDs exist, these will be marked up differently in the pending changes UI