M1.7: crash-recovery journal and restore dialog
Dirty buffers are written atomically to <data_dir>/recovery/<project-id>/ about 1 s after the last edit (at most 2 s while typing), from pump_vfs, never per keystroke. Entries are removed on save, close (also force), forced project close/open and recovery.discard. project.open emits recoveryAvailable; recovery.list/restore/discard; restored buffers are dirty and keep line ending and BOM. Corrupt entries are moved aside and reported as warning notifications. UI: restore dialog in ui/src/components/recovery (Restore all, Restore selected, Discard, time, changed-on-disk hint), catalog keys and runtime allow-list. Tests: crash/restore with CRLF + BOM, corrupt entries, removal paths, property test of random edits, headless control-channel test, Vitest for the dialog. Docs: architecture, parity, gaps, ROADMAP. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
6d976ed03e
commit
0b40eb90f8
27 changed files with 2222 additions and 27 deletions
|
|
@ -15,6 +15,8 @@ use std::collections::BTreeMap;
|
|||
use serde::Serialize;
|
||||
use serde_json::{Map, Value};
|
||||
|
||||
use crate::journal::EntryInfo;
|
||||
|
||||
/// A state change.
|
||||
#[derive(Debug, Clone, PartialEq, Eq, Serialize)]
|
||||
#[serde(
|
||||
|
|
@ -96,6 +98,13 @@ pub enum Event {
|
|||
/// Every token as `--lt-<name>` → CSS value.
|
||||
tokens: BTreeMap<String, String>,
|
||||
},
|
||||
/// The recovery journal of the project just opened holds unsaved texts
|
||||
/// from an earlier session; offer `recovery.restore` /
|
||||
/// `recovery.discard`.
|
||||
RecoveryAvailable {
|
||||
/// The entries, sorted by path.
|
||||
entries: Vec<EntryInfo>,
|
||||
},
|
||||
/// A message for the user, shown as a toast.
|
||||
Notification {
|
||||
/// Unique id of this notification, for dismissing it.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue