Shared `slotsTokenizer` for directive blocks
メンテナーはふだん 1 日以内に返信
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 20/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- markdown, typescript
- 領域
- frontend
調査の方向性
Start from the existing cut extension and container directive registration that call builder.configureMd; trace how each parses its body into Markdown-it tokens and where schema expressions are declared. Implement the shared router behind blockContentSlots and slotsTokenizer, then compare both token streams shown in the issue. Done when cut routes paragraphs/images and header routes actions/content, with preview and WYSIWYG specs accepting the same routed stream.
索引モデルが issue の本文から書いたものです。
説明
Edited by AI
"Generated" means mostly the model, "Edited" means mostly the author.
Problem
Different blocks split their Markdown body into several parts. Each part limits which content it accepts and how many items it holds. Implemented in each block's own contentTokenizer, this selection and routing logic is duplicated.
Solution
A shared slotsTokenizer function takes rules for named parts (slots) and returns a tokenizer for the existing contentTokenizer field of container directives.
The block declares its slots and their limits. The shared function parses the body, selects content and emits slot wrappers.
Contract
The field in ContainerDirectiveConfig from @diplodoc/directive:
contentTokenizer?: (
state: StateBlock,
content: BlockContent,
params: ContainerDirectiveParams,
) => void;
The directive handler calls it between the block's opening and closing tokens. The function adds the body tokens to state.tokens.
slotsTokenizer returns a function with this signature:
type SlotMatch = (group: readonly Token[]) => boolean;
type SlotRule = {
slot: string;
match: SlotMatch;
limit?: number;
className?: string;
};
declare function slotsTokenizer(
name: string,
rules: readonly SlotRule[],
): NonNullable<ContainerDirectiveConfig['contentTokenizer']>;
declare function byType(...types: string[]): SlotMatch;
name— directive name. The body is parsed withparentType<name>-directive, as by the default tokenizer.slot— unique slot name. The wrapper is a<slot>_open/<slot>_closepair with thedivtag.match— condition for content the slot accepts.limit— maximum number of groups in the slot per block instance: a positive integer, unlimited by default.className— optional CSS class of the wrapper.byType— matches the type of the group's first token.
A group is a standalone top-level token, or an opening token with everything up to its matching closing token. A group is moved as a whole.
Processing rules
- Groups are processed in source order.
- A group goes to the first slot whose
matchreturnstrueand whoselimitis not reached. - A group no slot accepts is dropped. A last slot with
match: () => truekeeps the remaining content. - Slots are emitted in rule order, and groups keep source order within a slot. Empty slots emit their wrappers too.
- Moved tokens get
level + 1. A wrapper'smapspans its groups. matchreceives the whole group withinline.childrenfilled, so it can check nested markup. Markdown-it fillschildrenin the coreinlinerule after block parsing, soslotsTokenizerfills them itself without duplicates after that rule runs.- Preview and WYSIWYG use the same token stream. Editor slot nodes accept the content their rules accept, including an empty slot.
Usage
registerContainerDirective(md, {
name: 'block',
match: () => true,
container: {tag: 'div', token: 'block'},
contentTokenizer: slotsTokenizer('block', [
{slot: 'block-a', match: byType('paragraph_open'), limit: 1},
{slot: 'block-b', match: byType('paragraph_open', 'bullet_list_open')},
]),
});
The first paragraph goes to block-a. Later paragraphs and bullet lists go to block-b. Everything else is dropped.
- 主要言語
- TypeScript
- スター
- 428
- フォーク
- 48
- 平均マージ
- 5日 15時間
- マージ済み PR(30日)
- 47
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
gravity-ui/markdown-editor のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
gravity-ui/markdown-editor#1452 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
gravity-ui/markdown-editor#1293 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
gravity-ui/markdown-editor#1129 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 72/100
gravity-ui/markdown-editor#1450 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
gravity-ui/markdown-editor#1331 ·
メンテナーはふだん 1 日以内に返信
gravity-ui/markdown-editor の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
tintinweb/pi-subagents#459 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
danielmiessler/LifeOS#2830 ·
メンテナーはふだん 6 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
freshframework/fresh#3920 ·
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
area: client enhancement priority: low
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
opensro-dev/opensro#3681 ·
メンテナーはふだん 1 日以内に返信