mirror of
https://github.com/VibedByKaKi/t3-code-android-nightly.git
synced 2026-10-10 04:11:15 +02:00
300f7f9d45
Co-authored-by: Julius Marminge <51714798+juliusmarminge@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Co-authored-by: Julius Marminge <julius0216@outlook.com>
42 lines
2.6 KiB
Markdown
42 lines
2.6 KiB
Markdown
# Composer coordinates and serialization
|
|
|
|
The draft store owns Markdown, while Tiptap owns the editing document. The rich-text
|
|
setting changes the installed extensions, so toggling it remounts the editor from the
|
|
stored draft. Plain mode must leave formatting markers literal. Rich mode preserves
|
|
whitespace and chip sources, but canonicalizes supported delimiters (`__` to `**`,
|
|
`_` to `*`) and checkbox case (`[X]` to `[x]`).
|
|
|
|
Store cursors are not ProseMirror positions: collapsed coordinates count a chip as one
|
|
character, expanded coordinates count its source text, and ProseMirror also counts
|
|
block boundaries. Keep conversion in [the document model](../../apps/web/src/composer-rich-text-doc.ts).
|
|
Empty paragraphs need real caret positions even though they contain no text. Markers
|
|
shown beside styled text are decorations, so offsets inside them clamp to the text edge.
|
|
|
|
Only replace editor content when the controlled text changes. Replacing it for a cursor
|
|
move creates undo entries and regenerates citation identities. Pending citation popovers
|
|
must wait until the requested draft has reached the editor before locating their chip.
|
|
|
|
Rich tasks split through native editor commands so marks and chips survive. Literal
|
|
lists use [store edits](../../apps/web/src/composer-list-continuation.ts). Newlines become
|
|
paragraph splits: trailing hard breaks otherwise appear to require two presses.
|
|
Programmatic moves must explicitly scroll the caret into view.
|
|
|
|
Clipboard text must come from the Markdown serializer, not DOM text: chip labels omit
|
|
the source and marker decorations are not content. Structured context records accompany
|
|
that text when available. Paste completes trailing chip delimiters and adds a leading
|
|
boundary when inserting a chip directly after text.
|
|
|
|
Block nodes (fences, lists, quotes, rules, headings) keep their exact Markdown
|
|
delimiters as node attributes, so the round trip is byte-identical and offsets
|
|
inside a delimiter clamp to the block's text like task and style markers. The
|
|
serializers write only what the grammar has: a quote holds paragraphs, a list
|
|
holds paragraphs and lists. So blocks may only form at a top-level paragraph.
|
|
Input rules check this, and Tiptap's own block chords (Mod-Shift-8, Mod-Alt-c,
|
|
and so on) are removed, because nesting a block the serializer cannot write
|
|
drops its text from the stored draft. The list grammar is the plain-mode
|
|
continuation's in [composer-list-continuation](../../apps/web/src/composer-list-continuation.ts);
|
|
keep the two in step.
|
|
|
|
Enter sends, so the fence handling in `handleKeyDown` must run before the send
|
|
handler: checked afterwards, a fence never opens and a newline inside one sends
|
|
the draft.
|