Shared `slotsTokenizer` for directive blocks
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- markdown, typescript
- Área
- frontend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 428
- Forks
- 48
- Merge medio
- 5 d 15 h
- PR fusionados (30 d)
- 47
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de gravity-ui/markdown-editor
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
gravity-ui/markdown-editor#1452 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
gravity-ui/markdown-editor#1293 ·
Los mantenedores suelen responder en 1 día
-
Markup mode: `colorify` does not detect existing `{color}(...)` wrapper when switching colorsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
gravity-ui/markdown-editor#1129 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
gravity-ui/markdown-editor#1450 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
gravity-ui/markdown-editor#1331 ·
Los mantenedores suelen responder en 1 día
Todos los issues de gravity-ui/markdown-editor
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tintinweb/pi-subagents#459 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
danielmiessler/LifeOS#2830 ·
Los mantenedores suelen responder en 6 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
freshframework/fresh#3920 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
area: client enhancement priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#3681 ·
Los mantenedores suelen responder en 1 día