Contrib.social

[PP-1] Create api slice for auto-save data (pending changes) and publishing all data

Open on Drupal.org →
Created on 3 December 2024, about 1 month ago

Overview

In 📌 Create AutoSave service and HTTP API to retrieve all entities with pending changes Active we're adding a controller to provide the list of current changes
In 📌 Create an endpoint to publish all auto-saved entities Active we added an endpoint for publishing all data

When these are both added we will need an API slice for fetching the list and a mutation for publishing all data

Proposed resolution

Create an api slice to `getAllPendingChanges` and `publishAllPendingChanges` that reads from and posts to the controllers respectively.
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

User interface changes

✨ Feature request
Status

Postponed

Version

0.0

Component

Page builder

Created by

🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024