Skip to content

Draft: #3526907 Concurrency control allow PATCH for region without validating other regions/main content

Ted Bowmanrequested to merge
concurrency-control-patch-region into concurrency-control

This against project/experience_builder!1127 (merged) to show how easy it would be to allow a PATCH request \Drupal\experience_builder\Controller\ApiLayoutController::patch() without validating all the auto-saves array that client has.

Please review the other merge request unless commenting where we should make this change for PATH

The UX effect of this would be that if I wanted to update the props of any component I would not get the new 409 error and the message that I don't have latest changes if something has changed if there are changes to any of the other regions besides the one with that contains the current component I am patching.

So this would very useful to get fewer errors because many users might be editing different main entities but all changing the regions.

Because of the way \Drupal\experience_builder\Controller\ApiLayoutController::post() works we would still have to validate all regions when adding new components, reordering components, or updating the Page Data form.

but this might be good stop gap until we can tackle Enable concurrent editing: Replace the postPreview action with atomic equivalents

Edited by Ted Bowman

Merge request reports