OptionalallowDefines allowed attributes of the given item.
OptionalallowInherits "allowed attributes" from other items.
Note that the item's "own" rules take precedence over "inherited" rules and can overwrite them.
OptionalallowDefines which other items are allowed inside this item.
OptionalallowInherits "allowed children" from other items.
Note that the item's "own" rules take precedence over "inherited" rules and can overwrite them.
OptionalallowDefines in which other items this item will be allowed.
OptionalallowInherits "allowed in" from other items.
Note that the item's "own" rules take precedence over "inherited" rules and can overwrite them.
OptionaldisallowDefines disallowed attributes for this item. Takes precedence over allow rules.
OptionaldisallowDefines which other items are disallowed inside this item. Takes precedence over allow rules.
OptionaldisallowDefines in which other items this item will be disallowed. Takes precedence over allow rules.
OptionalinheritA shorthand for allowContentOf, allowWhere, allowAttributesOf, inheritTypesFrom.
Note that the item's "own" rules take precedence over "inherited" rules and can overwrite them.
OptionalinheritInherits is* properties of other items.
Note that the item's "own" rules take precedence over "inherited" rules and can overwrite them.
OptionalisWhether this item is paragraph-like. Generally speaking, content is usually made out of blocks
like paragraphs, list items, images, headings, etc. All these elements are marked as blocks. A block
should not allow another block inside. Note: There is also the $block generic item which has isBlock set to true.
Most block type items will inherit from $block (through inheritAllFrom).
Read more about the block elements in the {@glink framework/deep-dive/schema#block-elements Block elements section} of the {@glink framework/deep-dive/schema Schema deep-dive} guide.
OptionalisAn item is a content when it always finds its way to the editor data output regardless of the number and type of its descendants.
Examples of content elements: $text, imageBlock, table, etc. (but not paragraph, heading1 or tableCell).
Note: An object is also a content element, so
module:engine/model/schema~ModelSchema#isContent isContent() returns true for object elements automatically.
Read more about content elements in the {@glink framework/deep-dive/schema#content-elements Content elements section} of the {@glink framework/deep-dive/schema Schema deep-dive} guide.
OptionalisWhether an item is "text-like" and should be treated as an inline node. Examples of inline elements:
$text, softBreak (<br>), etc.
Read more about the inline elements in the {@glink framework/deep-dive/schema#inline-elements Inline elements section} of the Schema deep-dive guide.
OptionalisIt can be understood as whether this element should not be split by Enter.
Examples of limit elements: $root, table cell, image caption, etc. In other words, all actions that happen inside
a limit element are limited to its content.
Read more about the limit elements in the {@glink framework/deep-dive/schema#limit-elements Limit elements section} of the {@glink framework/deep-dive/schema Schema deep-dive} guide.
OptionalisWhether an item is "self-contained" and should be treated as a whole. Examples of object elements:
imageBlock, table, video, etc.
Note: An object is also a limit, so
module:engine/model/schema~ModelSchema#isLimit isLimit() returns true for object elements automatically.
Read more about the object elements in the {@glink framework/deep-dive/schema#object-elements Object elements section} of the Schema deep-dive guide.
Optionalistrue when an element should be selectable as a whole by the user.
Examples of selectable elements: imageBlock, table, tableCell, etc.
Note: An object is also a selectable element, so
module:engine/model/schema~ModelSchema#isSelectable isSelectable() returns true for object elements automatically.
Read more about selectable elements in the {@glink framework/deep-dive/schema#selectable-elements Selectable elements section} of the {@glink framework/deep-dive/schema Schema deep-dive} guide.
A definition of a module:engine/model/schema~ModelSchema schema item.
You can define the following rules:
allowIn– Defines in which other items this item will be allowed.allowChildren– Defines which other items are allowed inside this item.allowAttributes– Defines allowed attributes of the given item.disallowIn– Defines in which other items this item will be disallowed.disallowChildren– Defines which other items are disallowed inside this item.disallowAttributes– Defines disallowed attributes of the given item.allowContentOf– Makes this item allow children that are also allowed in the specified items. This acknowledges disallow rules.allowWhere– Makes this item allowed where the specified items are allowed. This acknowledges disallow rules.allowAttributesOf– Inherits attributes from other items. This acknowledges disallow rules.inheritTypesFrom– Inheritsis*properties of other items.inheritAllFrom– A shorthand forallowContentOf,allowWhere,allowAttributesOf,inheritTypesFrom.The
is*propertiesThere are a couple commonly used
is*properties. Their role is to assign additional semantics to schema items.isBlock– Whether this item is paragraph-like. Generally speaking, content is usually made out of blocks like paragraphs, list items, images, headings, etc.isInline– Whether an item is "text-like" and should be treated as an inline node. Examples of inline elements:$text,softBreak(<br>), etc.isLimit– It can be understood as whether this element should not be split by Enter. Examples of limit elements:$root, table cell, image caption, etc. In other words, all actions that happen inside a limit element are limited to its content. All objects are treated as limit elements, too.isObject– Whether an item is "self-contained" and should be treated as a whole. Examples of object elements:imageBlock,table,video, etc. An object is also a limit, so module:engine/model/schema~ModelSchema#isLimitisLimit()returnstruefor object elements automatically.Read more about the meaning of these types in the {@glink framework/deep-dive/schema#defining-additional-semantics dedicated section of the Schema deep-dive} guide.
Generic items
There are several generic items (classes of elements) available:
$root,$container,$block,$blockObject,$inlineObject, and$text. They are defined as follows:They reflect typical editor content that is contained within one root, consists of several blocks (paragraphs, lists items, headings, images) which, in turn, may contain text inside.
By inheriting from the generic items you can define new items which will get extended by other editor features. Read more about generic types in the {@glink framework/deep-dive/schema Schema deep-dive} guide.
Example definitions
Allow
paragraphin roots and block quotes:Allow
paragrapheverywhere where$blockis allowed (i.e. in$root):Allow
paragraphinside a$rootand allow$textas aparagraphchild:The previous rule can be written in a shorter form using inheritance:
Make
imageBlocka block object, which is allowed everywhere where$blockis. Also, allowsrcandaltattributes in it:Make
captionallowed inimageBlockand make it allow all the content of$blocks (usually,$text). Also, mark it as a limit element so it cannot be split:Register
inlineImageas a kind of an inline object but disallow it inside captions:Make
listIteminherit all from$blockbut also allow additional attributes:Which translates to:
Tips
is*properties. They do not affect the allowed structures, but they can affect how the editor features treat your elements.