References to guides, categories and pages in rich text (#101) #150
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba!150
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/101-references"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #101.
Summary
Authors select words in rich text, choose the bookmark in the inline toolbar and pick a guide, category or page by searching. The reference is stored by id; readers see the target's current title (ADR-0020), with a preview card on hover, and the stored text, unlinked, where the target is gone or hidden from them. Decisions in ADR-0026.
Evidence
After:
e2e/references.spec.ts: author picks a guide by search → reader sees a link with the target's title and the card on hover → an unpublished rename neither shows nor is found by the search → after publishing, the new title shows → a guest sees the internal target as plain text.e2e/richText.spec.ts: each inline tool button keeps a contrast ≥ 3 under the pointer in dark mode (failed at 1.05 before the fix).pages.spec.ts"keys and paste in a column stay in the column", which is flaky ondevelopmenttoo (2 of 12 runs there, 0 of 12 on this branch).Merge Danger
Door: two-way
No migration; references live in the existing rich text JSON. Stored content without references renders as before.
Blast Radius: rich-text
Every rich text render now passes through the reference resolver (one extra query per kind only when a document has references), and the inline toolbar gains a button in every editor.
🤖 Generated with Claude Code