- Issue created by @tedbow
- 🇺🇸United States tedbow Ithaca, NY, USA
Postponing on 📌 [PP-1] Enforce conflict enforcement outside of tests and e2e tests Postponed because that issue end up having some back-end changes we would likely use here
As part of
📌
META: Conflict free concurrent editing
Active
we are actually going to make sure we prevent concurrent editing
for layout, page data and regions, we are handling this with
📌
Add rudimentary conflict prevention to the preview end-point
Active
and
📌
[PP-1] Enforce conflict enforcement outside of tests and e2e tests
Postponed
But the same problem exists for Javascript component and asset libraries.
if users open up the sam config entity in XB they will be overwriting each other's work with every auto-save
Return the latest auto-save to the client and do not allow an auto-save if they do not have the lastest version
We may want reload the auto-save version from the server for the global CSS when the user focuses the form because everyone will have the same copy
Active
0.0
Auto-save
Postponing on 📌 [PP-1] Enforce conflict enforcement outside of tests and e2e tests Postponed because that issue end up having some back-end changes we would likely use here