bvandeusenandClaude Opus 5
ce6a1093a3
The + button raised a capture sheet with a single text field. The editor is
a screen with a toolbar. So a note being WRITTEN could not be given a
colour, a reminder or a checklist — those live on the toolbar, and the sheet
had none. To make a checklist you wrote a note, saved it, reopened it, and
found a control you had never seen.
ComposeSheet is deleted. + opens the editor on an unsaved draft.
A draft is a real Note carrying DRAFT_ID (the empty string) rather than a
null. Note has eighteen fields and the editor reads eight of them; threading
nullability through all of that to express "not saved yet" would spread the
concept across a screen that should not have to know about it. A real id is
a uuid, so the sentinel cannot collide.
It becomes a row on its first save, and the first save is now an autosave:
the editor writes a second after typing stops. That is affordable because
2707054 made a body write stop costing a revision — before it, saving this
often would have meant a revision per second.
Autosave is also what makes materialisation work at all. Creating the note
on a toolbar tap instead races: the typed text lives in the field's own
state and only reaches the view model on flush, so the tap would create an
EMPTY note and lose what was written. With a one-second debounce the note
already exists by the time any button is reachable.
Three consequences worth naming:
- editingSession, bumped only when the editor opens on a DIFFERENT note.
The text field keys on it instead of note.id, because a draft's id changes
the moment it is first saved and re-keying on that would reset the field
to whatever the store just returned — discarding everything typed during
the write.
- The field is rememberSaveable now. A new note has nothing to fall back on,
and the old sheet used rememberSaveable for exactly this reason; the
editor inherits the requirement along with the job.
- draftDismissed, so a create still in flight cannot reopen an editor the
user has already closed.
Starting a checklist may create an empty note — a note named from its first
item is one this app already has. Colour and reminder are attributes OF a
note and need words first.
editor_body_hint becomes "Take a note…". It read "Note", which is a label on
a blank screen where the sheet's was an invitation.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>