feat(rich-text): preserve ordered list markers when unindenting out of a list

[henningmu]

Overview

Typing a number followed by a dot and a space at the start of a paragraph (e.g. the German date 17. Juli) triggers the ordered-list input rule, which swallows the typed number into the list's start attribute. Shift-Tab to undo the list conversion, removed the number entirely (17. Juli → Juli), with no way to recover it. This made it effectively impossible to start a line with such a date.

This PR adds a RichTextListItem extension (mirroring the RichTextOrderedList/RichTextBulletList pattern) that replaces the stock ListItem in RichTextKit. It only customizes Shift-Tab: when the lift takes the item out of an ordered list (as opposed to unindenting it into a parent list), the rendered marker is re-inserted as literal text at the start of the lifted paragraph — so Shift-Tab never destroys visible content.

Before	After
17. Juli + Shift-Tab → Juli	17. Juli + Shift-Tab → 17. Juli

Implementation notes:

Bullet lists are intentionally left untouched: the number is user-meaningful data, a bullet is not.

Related: Doist/Issues#20622

PR Checklist

• Pull request title follows the Conventional Commits Specification
• Added/updated unit test cases and/or end-to-end test cases

Test plan

• Manually, in the preview Storybook:
  • Open the Rich-text → Default story
  • Type 17. Juli at the start of an empty line (converts to an ordered list starting at 17)
  • Press Shift-Tab
    • Observe the paragraph reads 17. Juli as plain text
  • Press Tab/Shift-Tab inside nested and bullet lists
    • Observe unchanged behavior everywhere else

[netlify]

✅ Deploy Preview for doist-typist ready!

Name	Link
🔨 Latest commit	2e21d75
🔍 Latest deploy log	https://app.netlify.com/projects/doist-typist/deploys/6a69a676d1292400084b6679
😎 Deploy Preview	https://deploy-preview-1415--doist-typist.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[doistbot]

This PR adds a RichTextListItem extension that preserves ordered-list markers as literal text when Shift-Tab lifts an item out of a list — a nice fix for the date-at-start-of-line problem.

I also included a few optional follow-up notes in the details below.

Optional follow-up notes (3)

• src/extensions/rich-text/rich-text-list-item.ts:63: The editor.can().liftListItem(itemTypeName) guard at this line dry-runs the lift command's transaction logic to check feasibility, then editor.chain().liftListItem(itemTypeName) at line 75 runs the same logic again to actually apply it. The chain already handles failure — if liftListItem returns false, the chain returns false and the fallback this.editor.commands.liftListItem(this.name) on line 99 fires correctly. The guard adds no safety benefit (the lift happens before marker insertion, so there's no risk of partial execution) and doubles the lift computation on every Shift-Tab that reaches this path. Remove lines 63–65.
• src/extensions/rich-text/rich-text-list-item.test.ts:83: The describe block name says "when Shift-Tab does not lift the item out of a list," but the bullet-list test inside it (line 84) does lift the item out — it goes from <ul><li> to plain <p>. The describe name is only accurate for the nested ordered list test. Consider renaming to something like when marker preservation is not applicable or when Shift-Tab falls back to the default behavior.
• src/extensions/rich-text/rich-text-list-item.test.ts:47: The non-empty selection guard in liftOutOfOrderedListPreservingMarker (line 27 of rich-text-list-item.ts) is a deliberate safety behavior — it prevents ambiguous marker insertion when lifting a multi-item range — but no test covers it. Every test uses createEditorWithCaretAfter, which always creates a collapsed selection. A test that selects across two ordered-list items (e.g. via editor.commands.setTextSelection(from, to)) and asserts that Shift-Tab lifts without inserting a stray marker would protect against someone removing the guard. The existing harness makes this straightforward to add.

_{Share Feedback • Review Logs}

[rfgamaral]

@henningmu Looks good to me, left a few comments that I think are worth addressing, but non-blocking.

[henningmu]

Addressed both comments. Thanks, Ricardo 🙌

[doist-release-bot]

🎉 This PR is included in version 16.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀