DataController (engine/controller)
@ckeditor/ckeditor5-engine/src/controller/datacontroller
Controller for the data pipeline. The data pipeline controls how data is retrieved from the document and set inside it. Hence, the controller features two methods which allow to get and set data of the model using the given:
- data processor,
- downcast converters,
- upcast converters.
An instance of the data controller is always available in the editor.data
property:
editor.data.get( { rootName: 'customRoot' } ); // -> '<p>Hello!</p>'
Filtering
Properties
-
downcastDispatcher : DowncastDispatcher
module:engine/controller/datacontroller~DataController#downcastDispatcher
readonly
Downcast dispatcher used by the get method. Downcast converters should be attached to it.
-
htmlProcessor : HtmlDataProcessor
module:engine/controller/datacontroller~DataController#htmlProcessor
readonly
Data processor used specifically for HTML conversion.
-
Mapper used for the conversion. It has no permanent bindings, because these are created while getting data and ae cleared directly after the data are converted. However, the mapper is defined as a class property, because it needs to be passed to the
DowncastDispatcher
as a conversion API. -
Data model.
-
processor : DataProcessor
module:engine/controller/datacontroller~DataController#processor
Data processor used during the conversion. Same instance as
htmlProcessor
by default. Can be replaced at run time to handle different format, e.g. XML or Markdown. -
stylesProcessor : StylesProcessor
module:engine/controller/datacontroller~DataController#stylesProcessor
readonly
Styles processor used during the conversion.
-
upcastDispatcher : UpcastDispatcher
module:engine/controller/datacontroller~DataController#upcastDispatcher
readonly
Upcast dispatcher used by the set method. Upcast converters should be attached to it.
-
viewDocument : Document
module:engine/controller/datacontroller~DataController#viewDocument
readonly
The view document used by the data controller.
-
_viewWriter : DowncastWriter
module:engine/controller/datacontroller~DataController#_viewWriter
private readonly
The view downcast writer just for data conversion purposes, i.e. to modify the
viewDocument
.
Methods
-
constructor( model, stylesProcessor )
module:engine/controller/datacontroller~DataController#constructor
Creates a data controller instance.
Parameters
model : Model
Data model.
stylesProcessor : StylesProcessor
The styles processor instance.
-
addStyleProcessorRules( callback )
module:engine/controller/datacontroller~DataController#addStyleProcessorRules
Adds the style processor normalization rules.
You can implement your own rules as well as use one of the available processor rules:
- background:
addBackgroundRules
- border:
addBorderRules
- margin:
addMarginRules
- padding:
addPaddingRules
Parameters
callback : function
- background:
-
bind( bindProperties ) → Object
module:engine/controller/datacontroller~DataController#bind
mixed
Binds observable properties to other objects implementing the
Observable
interface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
button
and an associatedcommand
(bothObservable
).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
or even shorter:
button.bind( 'isEnabled' ).to( command );
which works in the following way:
button.isEnabled
instantly equalscommand.isEnabled
,- whenever
command.isEnabled
changes,button.isEnabled
will immediately reflect its value.
Note: To release the binding, use
unbind
.You can also "rename" the property in the binding by specifying the new name in the
to()
chain:button.bind( 'isEnabled' ).to( command, 'isWorking' );
It is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );
which corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );
The binding can include more than one observable, combining multiple data sources in a custom callback:
button.bind( 'isEnabled' ).to( command, 'isEnabled', ui, 'isVisible', ( isCommandEnabled, isUIVisible ) => isCommandEnabled && isUIVisible );
Using a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );
It is also possible to bind to the same property in an array of observables. To bind a
button
to multiple commands (alsoObservables
) so that each and every one of them must be enabled for the button to become enabled, use the following code:button.bind( 'isEnabled' ).toMany( [ commandA, commandB, commandC ], 'isEnabled', ( isAEnabled, isBEnabled, isCEnabled ) => isAEnabled && isBEnabled && isCEnabled );
Parameters
bindProperties : String
Observable properties that will be bound to other observable(s).
Returns
Object
The bind chain with the
to()
andtoMany()
methods.
-
decorate( methodName )
module:engine/controller/datacontroller~DataController#decorate
mixed
Turns the given methods of this object into event-based ones. This means that the new method will fire an event (named after the method) and the original action will be plugged as a listener to that event.
Read more in the dedicated guide covering the topic of decorating methods with some additional examples.
Decorating the method does not change its behavior (it only adds an event), but it allows to modify it later on by listening to the method's event.
For example, to cancel the method execution the event can be stopped:
class Foo { constructor() { this.decorate( 'method' ); } method() { console.log( 'called!' ); } } const foo = new Foo(); foo.on( 'method', ( evt ) => { evt.stop(); }, { priority: 'high' } ); foo.method(); // Nothing is logged.
Note: The high priority listener has been used to execute this particular callback before the one which calls the original method (which uses the "normal" priority).
It is also possible to change the returned value:
foo.on( 'method', ( evt ) => { evt.return = 'Foo!'; } ); foo.method(); // -> 'Foo'
Finally, it is possible to access and modify the arguments the method is called with:
method( a, b ) { console.log( `${ a }, ${ b }` ); } // ... foo.on( 'method', ( evt, args ) => { args[ 0 ] = 3; console.log( args[ 1 ] ); // -> 2 }, { priority: 'high' } ); foo.method( 1, 2 ); // -> '3, 2'
Parameters
methodName : String
Name of the method to decorate.
-
delegate( events ) → EmitterMixinDelegateChain
module:engine/controller/datacontroller~DataController#delegate
mixed
Delegates selected events to another
Emitter
. For instance:emitterA.delegate( 'eventX' ).to( emitterB ); emitterA.delegate( 'eventX', 'eventY' ).to( emitterC );
then
eventX
is delegated (fired by)emitterB
andemitterC
along withdata
:emitterA.fire( 'eventX', data );
and
eventY
is delegated (fired by)emitterC
along withdata
:emitterA.fire( 'eventY', data );
Parameters
events : String
Event names that will be delegated to another emitter.
Returns
-
destroy()
module:engine/controller/datacontroller~DataController#destroy
Removes all event listeners set by the DataController.
-
fire( eventOrInfo, [ args ] ) → *
module:engine/controller/datacontroller~DataController#fire
mixed
Fires an event, executing all callbacks registered for it.
The first parameter passed to callbacks is an
EventInfo
object, followed by the optionalargs
provided in thefire()
method call.Parameters
eventOrInfo : String | EventInfo
The name of the event or
EventInfo
object if event is delegated.[ args ] : *
Additional arguments to be passed to the callbacks.
Returns
*
By default the method returns
undefined
. However, the return value can be changed by listeners through modification of theevt.return
's property (the event info is the first param of every callback).
-
get( [ options ] = { [options.rootName], [options.trim] } ) → String
module:engine/controller/datacontroller~DataController#get
Returns the model's data converted by downcast dispatchers attached to
downcastDispatcher
and formatted by the data processor.Parameters
[ options ] : Object
Additional configuration for the retrieved data.
DataController
provides two optional properties:rootName
andtrim
. Other properties of this object are specified by various editor features.Properties[ options.rootName ] : String
Root name.
Defaults to
'main'
[ options.trim ] : String
Whether returned data should be trimmed. This option is set to
empty
by default, which means whenever editor content is considered empty, an empty string will be returned. To turn off trimming completely use'none'
. In such cases the exact content will be returned (for example a<p> </p>
for an empty editor).Defaults to
'empty'
Returns
String
Output data.
Fires
-
init( data ) → Promise
module:engine/controller/datacontroller~DataController#init
Sets the initial input data parsed by the data processor and converted by the view-to-model converters. Initial data can be only set to a document whose
version
is equal 0.Note This method is decorated which is used by e.g. collaborative editing plugin that syncs remote data on init.
When data is passed as a string, it is initialized on the default
main
root:dataController.init( '<p>Foo</p>' ); // Initializes data on the `main` root only, as no other is specified.
To initialize data on a different root or multiple roots at once, an object containing
rootName
-data
pairs should be passed:dataController.init( { main: '<p>Foo</p>', title: '<h1>Bar</h1>' } ); // Initializes data on both the `main` and `title` roots.
Parameters
data : String | Object.<String, String>
Input data as a string or an object containing the
rootName
-data
pairs to initialize data on multiple roots at once.
Returns
Promise
Promise that is resolved after the data is set on the editor.
Fires
-
listenTo( emitter, event, callback, [ options ] = { [options.priority] } )
module:engine/controller/datacontroller~DataController#listenTo
mixed
Registers a callback function to be executed when an event is fired in a specific (emitter) object.
Events can be grouped in namespaces using
:
. When namespaced event is fired, it additionally fires all callbacks for that namespace.// myEmitter.on( ... ) is a shorthand for myEmitter.listenTo( myEmitter, ... ). myEmitter.on( 'myGroup', genericCallback ); myEmitter.on( 'myGroup:myEvent', specificCallback ); // genericCallback is fired. myEmitter.fire( 'myGroup' ); // both genericCallback and specificCallback are fired. myEmitter.fire( 'myGroup:myEvent' ); // genericCallback is fired even though there are no callbacks for "foo". myEmitter.fire( 'myGroup:foo' );
An event callback can stop the event and set the return value of the
fire
method.Parameters
emitter : Emitter
The object that fires the event.
event : String
The name of the event.
callback : function
The function to be called on event.
[ options ] : Object
Additional options.
Properties[ options.priority ] : PriorityString | Number
The priority of this event callback. The higher the priority value the sooner the callback will be fired. Events having the same priority are called in the order they were added.
Defaults to
'normal'
Defaults to
{}
-
off( event, callback )
module:engine/controller/datacontroller~DataController#off
mixed
Stops executing the callback on the given event. Shorthand for
this.stopListening( this, event, callback )
.Parameters
event : String
The name of the event.
callback : function
The function to stop being called.
-
on( event, callback, [ options ] = { [options.priority] } )
module:engine/controller/datacontroller~DataController#on
mixed
Registers a callback function to be executed when an event is fired.
Shorthand for
this.listenTo( this, event, callback, options )
(it makes the emitter listen on itself).Parameters
event : String
The name of the event.
callback : function
The function to be called on event.
[ options ] : Object
Additional options.
Properties[ options.priority ] : PriorityString | Number
The priority of this event callback. The higher the priority value the sooner the callback will be fired. Events having the same priority are called in the order they were added.
Defaults to
'normal'
Defaults to
{}
-
once( event, callback, [ options ] = { [options.priority] } )
module:engine/controller/datacontroller~DataController#once
mixed
Registers a callback function to be executed on the next time the event is fired only. This is similar to calling
on
followed byoff
in the callback.Parameters
event : String
The name of the event.
callback : function
The function to be called on event.
[ options ] : Object
Additional options.
Properties[ options.priority ] : PriorityString | Number
The priority of this event callback. The higher the priority value the sooner the callback will be fired. Events having the same priority are called in the order they were added.
Defaults to
'normal'
Defaults to
{}
-
parse( data, [ context ] ) → DocumentFragment
module:engine/controller/datacontroller~DataController#parse
Returns the data parsed by the data processor and then converted by upcast converters attached to the
upcastDispatcher
.Parameters
data : String
Data to parse.
[ context ] : SchemaContextDefinition
Base context in which the view will be converted to the model. See:
convert
.Defaults to
'$root'
Returns
DocumentFragment
Parsed data.
Related:
-
registerRawContentMatcher( pattern )
module:engine/controller/datacontroller~DataController#registerRawContentMatcher
Registers a
MatcherPattern
on an htmlProcessor and a processor for view elements whose content should be treated as raw data and not processed during the conversion from DOM to view elements.The raw data can be later accessed by the view element custom property
"$rawContent"
.Parameters
pattern : MatcherPattern
Pattern matching all view elements whose content should be treated as a raw data.
-
set( data, [ options ] = { [options.batchType] } )
module:engine/controller/datacontroller~DataController#set
Sets the input data parsed by the data processor and converted by the view-to-model converters. This method can be used any time to replace existing editor data with the new one without clearing the document history.
This method also creates a batch with all the changes applied. If all you need is to parse data, use the
parse
method.When data is passed as a string it is set on the default
main
root:dataController.set( '<p>Foo</p>' ); // Sets data on the `main` root, as no other is specified.
To set data on a different root or multiple roots at once, an object containing
rootName
-data
pairs should be passed:dataController.set( { main: '<p>Foo</p>', title: '<h1>Bar</h1>' } ); // Sets data on the `main` and `title` roots as specified.
To set the data with a preserved undo stack and add the change to the undo stack, set
{ isUndoable: true }
as abatchType
option.dataController.set( '<p>Foo</p>', { batchType: { isUndoable: true } } );
Parameters
data : String | Object.<String, String>
Input data as a string or an object containing the
rootName
-data
pairs to set data on multiple roots at once.[ options ] : Object
Options for setting data.
Properties[ options.batchType ] : Object
The batch type that will be used to create a batch for the changes applied by this method. By default, the batch will be set as not undoable and the undo stack will be cleared after the new data is applied (all undo steps will be removed). If the batch type
isUndoable
flag is be set totrue
, the undo stack will be preserved instead and not cleared when new data is applied.
Defaults to
{}
Fires
-
stopDelegating( [ event ], [ emitter ] )
module:engine/controller/datacontroller~DataController#stopDelegating
mixed
Stops delegating events. It can be used at different levels:
- To stop delegating all events.
- To stop delegating a specific event to all emitters.
- To stop delegating a specific event to a specific emitter.
Parameters
[ event ] : String
The name of the event to stop delegating. If omitted, stops it all delegations.
[ emitter ] : Emitter
(requires
event
) The object to stop delegating a particular event to. If omitted, stops delegation ofevent
to all emitters.
-
stopListening( [ emitter ], [ event ], [ callback ] )
module:engine/controller/datacontroller~DataController#stopListening
mixed
Stops listening for events. It can be used at different levels:
- To stop listening to a specific callback.
- To stop listening to a specific event.
- To stop listening to all events fired by a specific object.
- To stop listening to all events fired by all objects.
Parameters
[ emitter ] : Emitter
The object to stop listening to. If omitted, stops it for all objects.
[ event ] : String
(Requires the
emitter
) The name of the event to stop listening to. If omitted, stops it for all events fromemitter
.[ callback ] : function
(Requires the
event
) The function to be removed from the call list for the givenevent
.
-
stringify( modelElementOrFragment, [ options ] ) → String
module:engine/controller/datacontroller~DataController#stringify
Returns the content of the given model's element or model document fragment converted by the downcast converters attached to the
downcastDispatcher
and formatted by the data processor.Parameters
modelElementOrFragment : Element | DocumentFragment
The element whose content will be stringified.
[ options ] : Object
Additional configuration passed to the conversion process.
Returns
String
Output data.
-
toModel( viewElementOrFragment, [ context ] ) → DocumentFragment
module:engine/controller/datacontroller~DataController#toModel
Returns the result of the given view element or view document fragment converted by the view-to-model converters, wrapped by
DocumentFragment
.When marker elements were converted during the conversion process, it will be set as a document fragment's static markers map.
Parameters
viewElementOrFragment : Element | DocumentFragment
The element or document fragment whose content will be converted.
[ context ] : SchemaContextDefinition
Base context in which the view will be converted to the model. See:
convert
.Defaults to
'$root'
Returns
DocumentFragment
Output document fragment.
-
toView( modelElementOrFragment, [ options ] ) → DocumentFragment
module:engine/controller/datacontroller~DataController#toView
Returns the content of the given model element or model document fragment converted by the downcast converters attached to
downcastDispatcher
into a view document fragment.Parameters
modelElementOrFragment : Element | DocumentFragment
Element or document fragment whose content will be converted.
[ options ] : Object
Additional configuration that will be available through the
options
during the conversion process.Defaults to
{}
Returns
DocumentFragment
Output view DocumentFragment.
-
unbind( [ unbindProperties ] )
module:engine/controller/datacontroller~DataController#unbind
mixed
Removes the binding created with
bind
.// Removes the binding for the 'a' property. A.unbind( 'a' ); // Removes bindings for all properties. A.unbind();
Parameters
[ unbindProperties ] : String
Observable properties to be unbound. All the bindings will be released if no properties are provided.
-
_addEventListener( event, callback, [ options ] = { [options.priority] } )
module:engine/controller/datacontroller~DataController#_addEventListener
protected mixed
Adds callback to emitter for given event.
Parameters
event : String
The name of the event.
callback : function
The function to be called on event.
[ options ] : Object
Additional options.
Properties[ options.priority ] : PriorityString | Number
The priority of this event callback. The higher the priority value the sooner the callback will be fired. Events having the same priority are called in the order they were added.
Defaults to
'normal'
Defaults to
{}
-
_removeEventListener( event, callback )
module:engine/controller/datacontroller~DataController#_removeEventListener
protected mixed
Removes callback from emitter for given event.
Parameters
event : String
The name of the event.
callback : function
The function to stop being called.
-
_checkIfRootsExists( rootNames ) → Boolean
module:engine/controller/datacontroller~DataController#_checkIfRootsExists
private
Checks whether all provided root names are actually existing editor roots.
Parameters
rootNames : Array.<String>
Root names to check.
Returns
Boolean
Whether all provided root names are existing editor roots.
Events
-
change:{property}( eventInfo, name, value, oldValue )
module:engine/controller/datacontroller~DataController#event:change:{property}
mixed
Fired when a property changed value.
observable.set( 'prop', 1 ); observable.on( 'change:prop', ( evt, propertyName, newValue, oldValue ) => { console.log( `${ propertyName } has changed from ${ oldValue } to ${ newValue }` ); } ); observable.prop = 2; // -> 'prop has changed from 1 to 2'
Parameters
eventInfo : EventInfo
An object containing information about the fired event.
name : String
The property name.
value : *
The new property value.
oldValue : *
The previous property value.
-
get( eventInfo )
module:engine/controller/datacontroller~DataController#event:get
Event fired after the get() method has been run.
-
init( eventInfo )
module:engine/controller/datacontroller~DataController#event:init
An event fired after the
init()
method was run. It can be listened to in order to adjust or modify the initialization flow. However, if theinit
event is stopped or prevented, theready
event should be fired manually. -
ready( eventInfo )
module:engine/controller/datacontroller~DataController#event:ready
Event fired once the data initialization has finished.
Parameters
eventInfo : EventInfo
An object containing information about the fired event.
-
set( eventInfo )
module:engine/controller/datacontroller~DataController#event:set
An event fired after set() method has been run.
-
set:{property}( eventInfo, name, value, oldValue )
module:engine/controller/datacontroller~DataController#event:set:{property}
mixed
Fired when a property value is going to be set but is not set yet (before the
change
event is fired).You can control the final value of the property by using the event's
return
property.observable.set( 'prop', 1 ); observable.on( 'set:prop', ( evt, propertyName, newValue, oldValue ) => { console.log( `Value is going to be changed from ${ oldValue } to ${ newValue }` ); console.log( `Current property value is ${ observable[ propertyName ] }` ); // Let's override the value. evt.return = 3; } ); observable.on( 'change:prop', ( evt, propertyName, newValue, oldValue ) => { console.log( `Value has changed from ${ oldValue } to ${ newValue }` ); } ); observable.prop = 2; // -> 'Value is going to be changed from 1 to 2' // -> 'Current property value is 1' // -> 'Value has changed from 1 to 3'
Note: The event is fired even when the new value is the same as the old value.
Parameters
eventInfo : EventInfo
An object containing information about the fired event.
name : String
The property name.
value : *
The new property value.
oldValue : *
The previous property value.
Every day, we work hard to keep our documentation complete. Have you spotted an outdated information? Is something missing? Please report it via our issue tracker.