@stesura/core/schema

No inline children at all — the block renders as a bare trailing break.

ProseMirror renders a br.ProseMirror-trailingBreak inside this block.

Ends in a non-text inline node other than a hard break. The trailing <br> renders after it, so an ::after pilcrow would land on the next line (MT-12); these blocks get a widget marker instead (see plugins/invisible-characters/pilcrow-decorations.ts).

Contains a floated positioned object (floating family), so the block must contain its float.

At least one child carries the track-changes deletion mark.

Every child carries the deletion mark — nothing renders in show-off mode.

DrawingML passed through untouched (a group, chart, SmartArt…).

A fill-in prompt (Word’s content-control placeholder text).

A Word field with no node of its own; field is the template variable.

Word’s SEQ field: a caption’s number (field is taken by automation).

Points, matching the textStyle attr.

Anchor/body attribute holding the note ref (not “id” — the uniqueId plugin owns that).

Custom node specs, merged over the core set (same key replaces the core node). Use StesuraNodeSpec for completion on Stesura spec keys (e.g. spacingRole).

Custom mark specs, merged over the core set.

Node names to leave out, applied after nodes is merged. A core node must belong to an EXCLUDABLE_NODE_FAMILIES family, excluded whole; nodes added through nodes can always be excluded. Grants in globalAttributes.nodes for an excluded node are dropped with it. Throws a RangeError otherwise, on unknown names, and when a remaining content expression names an excluded node.

Global attributes: reusable attr bundles (numbering, spacing, formatting…) merged into node specs.

• definitions registers custom global attributes. A key colliding with a core attribute is ignored with an error.
• nodes adjusts which node types carry each attribute, as a delta on the defaults: true grants, false revokes, absent keeps the default. uniqueId cannot be configured (pagination requires ids on all blocks). Invalid config only logs. A node spec or custom definition declaring a reserved gate attr name throws a RangeError, since it would silently inherit plugin behavior.

Direct-formatting attrs to turn off, e.g. { indent: false }: the attr stays in the schema (its family’s gates key on it) but is never set directly, so the value comes from the style chain. Commands, Tab, the ruler, the paragraph panel, paste and DOCX import step aside, and directFormattingPlugin clears what still arrives. The derived indent of numbered blocks is unaffected.

Spacing-plugin role. When absent, an unspaced wrapper-shaped node (block node with block content, not an atom) is "passThrough" and everything else is a "boundary". Set it only to override that inference.

"atomic": pagination measures this textblock as one unbreakable box instead of splitting it into lines (a rendered formula or diagram whose text content is its source).

A wrapper (block node with block content) that pagination places whole when it fits a page: pushed to the next page rather than split. One taller than a page still splits between its children.

Spacing (px) for a spaced node with neither its own spacing nor a style providing one, e.g. a callout. Collapses with its neighbors’ like any other.

doc only: the direct-formatting attrs the schema turns off (see allowsDirectFormatting).

The content expression for this node, as described in the schema guide . When not given, the node does not allow any content.

The marks that are allowed inside of this node. May be a space-separated string referring to mark names or groups, "_" to explicitly allow all marks, or "" to disallow marks. When not given, nodes with inline content default to allowing all marks, other nodes default to not allowing marks.

The group or space-separated groups to which this node belongs, which can be referred to in the content expressions for the schema.

Should be set to true for inline nodes. (Implied for text nodes.)

Can be set to true to indicate that, though this isn’t a leaf node , it doesn’t have directly editable content and should be treated as a single unit in the view.

The attributes that nodes of this type get.

Controls whether nodes of this type can be selected as a node selection . Defaults to true for non-text nodes.

Determines whether nodes of this type can be dragged without being selected. Defaults to false.

Can be used to indicate that this node contains code, which causes some commands to behave differently.

Controls way whitespace in this a node is parsed. The default is "normal", which causes the DOM parser  to collapse whitespace in normal mode, and normalize it (replacing newlines and such with spaces) otherwise. "pre" causes the parser to preserve spaces inside the node. When this option isn’t given, but code is true, whitespace will default to "pre". Note that this option doesn’t influence the way the node is rendered—that should be handled by toDOM and/or styling.

Determines whether this node is considered an important parent node during replace operations (such as paste). Non-defining (the default) nodes get dropped when their entire content is replaced, whereas defining nodes persist and wrap the inserted content.

In inserted content the defining parents of the content are preserved when possible. Typically, non-default-paragraph textblock types, and possibly list items, are marked as defining.

When enabled, enables both definingAsContext and definingForContent.

When enabled (default is false), the sides of nodes of this type count as boundaries that regular editing operations, like backspacing or lifting, won’t cross. An example of a node that should probably have this enabled is a table cell.

Defines the default way a node of this type should be serialized to DOM/HTML (as used by DOMSerializer.fromSchema). Should return a DOM node or an array structure  that describes one, with an optional number zero (“hole”) in it to indicate where the node’s content should be inserted.

For text nodes, the default is to create a text DOM node. Though it is possible to create a serializer where text is rendered differently, this is not supported inside the editor, so you shouldn’t override that in your text node spec.

Associates DOM parser information with this node, which can be used by DOMParser.fromSchema to automatically derive a parser. The node field in the rules is implied (the name of this node will be filled in automatically). If you supply your own parser, you do not need to also specify parsing rules in your schema.

Defines the default way a node of this type should be serialized to a string representation for debugging (e.g. in error messages).

Defines the default way a leaf node  of this type should be serialized to a string (as used by Node.textBetween and Node.textContent).

A single inline node in a schema can be set to be a linebreak equivalent. When converting between block types that support the node and block types that don’t but have whitespace set to "pre", setBlockType will convert between newline characters to or from linebreak nodes as appropriate.