[WJ-1020] Require passing in last revision ID for page operations #2117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a safety measure to protect against the following case:
Page locking does not help here since at no point are Alice and Bob attempting to commit the page at the same time. By requiring the frontend pass in the last revision ID for the page (which is already received by framerail as part of the page data), we ensure that if someone has an old version of the page locally loaded in their browser, they are effectively forced to reload if the page has been edited since.
This revision ID is only required for "destructive" operations, like edits, deletes, rollbacks, etc, where a user may possibly take a different action if they knew the page had been updated in the meantime.
I plan to make a similar change for file operations (see WJ-1281).