An item's revisions are stored and served, and no screen shows them.
Current state: handleRevisionList answers with an item's revisions newest first and handleRevisionGet returns one with its content. A type carries a setting for how many to keep. Nothing in the admin lists them, so the only way to read one is to call the API by hand.
Proposal: give the editor a control opening the item's history, naming when each revision was saved and who saved it, and letting one be read beside the current text. Restoring a revision is a separate decision and stays out of this.
Trigger: the admin gaps reviewed after 0.5.0, which the translations cycle deferred.
An item's revisions are stored and served, and no screen shows them.
Current state:
handleRevisionListanswers with an item's revisions newest first andhandleRevisionGetreturns one with its content. A type carries a setting for how many to keep. Nothing in the admin lists them, so the only way to read one is to call the API by hand.Proposal: give the editor a control opening the item's history, naming when each revision was saved and who saved it, and letting one be read beside the current text. Restoring a revision is a separate decision and stays out of this.
Trigger: the admin gaps reviewed after 0.5.0, which the translations cycle deferred.