[PP-1] Enforce conflict enforcement outside of tests and e2e tests

Created on 28 May 2025, 6 days ago

Overview

Follow-up to πŸ“Œ Add rudimentary conflict prevention to the preview end-point Active
In that issue we put in logic to throw an exception if client didn't send the latest auto-save hash for the entity and regions. This prevents 2 users for editing at the same time and wiping out each others changes

Trying to get the e2e tests to pass I discovered that rapid fire requests could cause this exception to be trigger without only 1 user editing the page.

So we decided to scope #3490565 to just the backend parts

Proposed resolution

In \Drupal\experience_builder\Controller\ApiLayoutController::validateAutoSaves() remove the special casing for phpunit tests.
Bring back the logic that was taken out of πŸ“Œ Add rudimentary conflict prevention to the preview end-point Active to send the autoSaves key from the client(commit link soon)
Implement system to handle rapid fire requests

User interface changes

πŸ“Œ Task
Status

Postponed

Version

0.0

Component

Page builder

Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024