- Issue created by @tedbow
- Merge request !1264Draft: Resolve #3532056 On Patch validate conflict region only → (Open) created by tedbow
- 🇺🇸United States tedbow Ithaca, NY, USA
We don't have to do this before beta but there is nothing blocking it now
Follow-up to
📌
[PP-1] Enforce conflict enforcement outside of tests and e2e tests
Postponed
where we threw a conflict exception in \Drupal\experience_builder\Controller\ApiLayoutController::validateAutoSaves() if the client didn't have the latest auto-saves of all of the entities on the page, the main entity and the regions. For \Drupal\experience_builder\Controller\ApiLayoutController::patch() it would have been easy to just validate the region containing the component being updated but it was decided that it was safer to validate all entities because we could then prompt the user to reload the browser and ensure the client state is up-to-date
Decide if we want up only validate the region or entity containing the component in
📌
Replace the postPreview action with atomic equivalents
Active
\Drupal\experience_builder\Controller\ApiLayoutController::patch() and or if want to wait allow concurrent editing in [
Postponed
0.0
Auto-save
We don't have to do this before beta but there is nothing blocking it now