@mflorea I think we still need to improve the RT mode and continue to make it the default.
I think there’s a way to solve the cancel issue + the too many revisions one.
What about the following:
- I make some changes in RT, a revision is created (autosave)
- I make another change and autosave kicks in. However since there was another change done with my user, the code meres the 2 change into a single revision (ie we end up with a singe revision containing the 2 change sets). Ofc this merge stops as soon as a revision is made by someone else, but can resume if again there are contiguous revisions done by a given user.
- Also, during the merge of revisions, if the diff is empty, then delete the revision altogether. This would solve the issue of cancelling leaving revisions behind: you make some changes, you undo them (using the WYSIWYG undo feature for ex) and after you click done (or the autosave kicks in), there’s no revision left.
So to sum up, we could implement:
- The Done button not adding a revision if there’s no changes done
- The revision merge for contiguous changes done by the same user, including the revision deletion if 2 changes negate each other
Then, later, we could discuss implementing other improvements such as:
3) Revert changes in the “Recent Changes” dropdown
4) Add the ability to set a message on a past revision, in the “Recent Changes” dropdown (ie it should show both the revisions and their messages + have a way to set a message). Side note: we could also allow admins or users with PR the ability to change the message for past revisions in the history view in docextra.
WDYT?
Thanks