Use case or problem
Before restoring a snapshot, I need to see how it differs from the current file: which changes would be reverted and which later edits would be lost.
When selecting a snapshot and enabling “Show changes”, the comparison appears to be against the preceding snapshot. This helps trace individual revisions, but does not show the effect of restoring an older snapshot over the current file.
The latest snapshot can represent the current file if no edits have occurred since it was captured. However, changes made since the latest snapshot are not included. This depends on snapshot timing, the configured interval, and subsequent edits.
Proposed solution
1. Quick reference selection
Add a selector: “Compare with: Current file / Previous snapshot”.
Comparing with the current file would be a useful default when assessing a restoration.
2. Arbitrary version selection
Add checkboxes beside the history entries, allowing exactly two comparison endpoints to be selected. Include the current file as a separate, clearly labelled entry.
This would support:
-
Current file ↔ latest snapshot: Review changes since the last snapshot.
-
Current file ↔ any older snapshot: Assess a potential restoration.
-
Any snapshot ↔ another snapshot: Review changes across a chosen period.
The interface could follow familiar Git GUI conventions: clearly label both endpoints, show snapshot timestamps, and make the direction of additions and deletions explicit. No Git integration is required.
The quick selector would address the basic recovery use case; arbitrary selection would provide additional flexibility.