OptionalskipIf false, comment nodes will be converted to $comment. Otherwise comment nodes are ignored.
Registers a module:engine/view/matcher~MatcherPattern for view elements whose content should be treated as raw data
and its content should be converted to a
module:engine/view/element~ViewElement#getCustomProperty custom property of a view element called "$rawContent" while
converting #toView to view.
Pattern matching all view elements whose content should be treated as plain text.
Converts a module:engine/view/documentfragment~ViewDocumentFragment document fragment to data.
The document fragment to be processed.
Converts the data to a module:engine/view/documentfragment~ViewDocumentFragment document fragment.
The data to be processed.
If the processor is set to use marked fillers, it will insert fillers wrapped in <span> elements
(<span data-cke-filler="true"> </span>) instead of regular characters.
This mode allows for more precise handling of block fillers (so they do not leak into the editor content) but bloats the editor data with additional markup.
This mode may be required by some features and will be turned on by them automatically.
Whether to use the default or marked block fillers.
The data processor interface. It should be implemented by actual data processors.
Each data processor implements a certain format of the data. For example, {@glink features/markdown Markdown data processor} will convert the data (a Markdown string) to a module:engine/view/documentfragment~ViewDocumentFragment document fragment and back.
Note: While the CKEditor 5 architecture supports changing the data format, in most scenarios we do recommend sticking to the default format which is HTML (supported by the module:engine/dataprocessor/htmldataprocessor~HtmlDataProcessor). HTML remains the best standard for rich-text data.
And please do remember – using Markdown does not automatically make your application/website secure.