API des plugins

The plugin contract version this was written against.

Checked at registration, so a plugin from a future contract fails loudly by name instead of misbehaving. It also lets v1 and v2 plugins run side by side during a migration, rather than every author breaking on one flag day.

import { PLUGIN_API_VERSION } from '@nbe/core'
const myBlock = { apiVersion: PLUGIN_API_VERSION, schema: { … } }

Markdown shortcuts that turn a paragraph into this block as you type — `\`\`\`` for code, the way `- ` makes a list.

Consulted before the built-in table, so a plugin may claim a prefix. It lives on the model half rather than the view because autoformat is a core command: a headless host applying an edit gets the same behaviour.

Static HTML for export and server rendering.

Returns a string rather than a live element, so it runs with no DOM and the same block renders identically in a CLI, on a server and in a browser.

Document invariants this block type repairs, run on every transaction that changed structure.

The extension point a table forced into existence, and the one a block with *internal* structure cannot do without: a row that lost a cell, a container left empty, a span pointing at a row that no longer exists. It runs on the model, so a headless import is normalized exactly like a keystroke — ProseMirror's `fixTables` is the same idea, exposed as a command because its plugins cannot reach the state's apply loop. Write it as a *repair*, not a validation: read the doc, emit the ops that make it legal through `tx`, return whether you emitted any. It must be idempotent — it will see its own output on the next transaction.

normalize: (doc, tx) => {
  let changed = false
  for (const row of shortRows(doc)) { tx.op(padRow(row)); changed = true }
  return changed
}

The block's declarative description: type, version, whether it carries inline text, its default props.

JSON-serializable and free of behaviour on purpose. The static renderer and a future Swift port consume it without executing any JavaScript, which they could not do if rendering functions lived inside it.

Editing-surface behaviour. Lives in the `@nbe/dom` layer, so it is typed as unknown here and refined there — `core` must never depend on the DOM.

Recognise this block in markdown. Consulted in precedence order, and the first matching rule wins.

Set when this format cannot represent the block faithfully. Read by tooling and by the docs table — never at runtime — so the loss is discoverable instead of discovered.