Skip to content

docs(rust): plan for Swift's feature set, and who owns each milestone - #150

Open
tmm wants to merge 1 commit into
rust-property-sequencesfrom
rust-plan-swift-parity
Open

tmm wants to merge 1 commit into
rust-property-sequencesfrom
rust-plan-swift-parity

Conversation

@tmm

@tmm tmm commented Nov 14, 2026

Copy link
Copy Markdown
Member

Description

DESIGN.md planned the whole of JS, ending with a Yjs binding (M6). tmm
narrowed the target: parity with what the Swift port supports first, with
both ports moving toward the rest of JS later as apps need it.

The plan now says so:

  • It drops @lexical/yjs, @lexical/y, @lexical/table,
    @lexical/code-shiki, @lexical/mdast and @lexical/offset, which
    Swift has none of.
  • M6 becomes the rest of Swift's feature set, and the feature table gains
    clipboard, mark and devtools.
  • It names the Amp thread that owns each milestone: the Rust port thread
    (M1, M3, M6 and the merges), the HTML thread (M4) and the Markdown thread
    (M5, with Markdown shortcuts in both playgrounds).

Test plan

Documentation only. npx prettier --check rust/DESIGN.md passes.

Stacked on #149.

## Description

DESIGN.md planned the whole of JS, ending with a Yjs binding (M6). tmm
narrowed the target: parity with what the Swift port supports first, with
both ports moving toward the rest of JS later as apps need it.

The plan now says so:

- It drops `@lexical/yjs`, `@lexical/y`, `@lexical/table`,
  `@lexical/code-shiki`, `@lexical/mdast` and `@lexical/offset`, which
  Swift has none of.
- M6 becomes the rest of Swift's feature set, and the feature table gains
  `clipboard`, `mark` and `devtools`.
- It names the Amp thread that owns each milestone: the Rust port thread
  (M1, M3, M6 and the merges), the HTML thread (M4) and the Markdown thread
  (M5, with Markdown shortcuts in both playgrounds).

## Test plan

Documentation only. `npx prettier --check rust/DESIGN.md` passes.

Amp-Thread-ID: https://ampcode.com/threads/T-16d45229-bfa8-417a-a091-d3e3888d830d

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants