AnnotationsUIs (comments/annotations)
@ckeditor/ckeditor5-comments/src/annotations/annotationsuis
A repository of annotations UIs.
The main entry point for registering UIs and activating the annotations UI(s), which display annotation views.
To register a custom annotations UI use following code in the annotations UI plugin init()
function:
const annotationsUIs = editor.plugins.get( 'annotationsUIs' );
annotationsUIs.register( customAnnotationsUIPlugin );
Note that the custom annotations UI must implement the AnnotationsUI
interface.
To activate an annotations UI, use the switchTo( uiName )
method. This method activates the given UI and deactivates all the other UIs.
All annotations will be handled by the activated UI.
It is also possible to activate multiple annotations UIs at the same time and make the UIs handle different sets of annotations.
To do that, use the activate( uiName, filter )
method.
// Suggestions annotations are shown inline in a balloon:
annotationsUIs.activate( 'inline', annotation => annotation.type.startsWith( 'suggestion' ) );
// At the same time, comments annotations are shown in a sidebar:
annotationsUIs.activate( 'wideSidebar', annotation => annotation.type === 'comment' );
Limitations:
- Some annotations UI plugins might collide with each other (like
NarrowSidebar
andWideSidebar
that operates on the same sidebar). They cannot be activated at the same time. - It is not possible to display the same annotation in two different annotations UIs. In this scenario an error will be thrown.
Filtering
Properties
-
activeUIs : Set<string>
module:comments/annotations/annotationsuis~AnnotationsUIs#activeUIs
-
readonly inherited
context : ContextInterface
module:comments/annotations/annotationsuis~AnnotationsUIs#context
The context or editor instance.
Static properties
-
readonly inherited static
isContextPlugin : true
module:comments/annotations/annotationsuis~AnnotationsUIs.isContextPlugin
-
readonly static
isOfficialPlugin : true
module:comments/annotations/annotationsuis~AnnotationsUIs.isOfficialPlugin
-
readonly static
isPremiumPlugin : true
module:comments/annotations/annotationsuis~AnnotationsUIs.isPremiumPlugin
-
readonly static
pluginName : 'AnnotationsUIs'
module:comments/annotations/annotationsuis~AnnotationsUIs.pluginName
-
readonly static
requires : readonly tuple
module:comments/annotations/annotationsuis~AnnotationsUIs.requires
Methods
-
constructor( context )
module:comments/annotations/annotationsuis~AnnotationsUIs#constructor
-
activate( uiName, filter ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#activate
Activates an annotations UI.
Note that the custom annotations UI should be registered before the activation.
The
filter
parameter can be used to display on some of the annotations in the given annotations UI. Thanks to that, all annotations can be split into various annotations UIs.The
filter
function takes anAnnotation
instance as the first and only parameter, and should returntrue
if that annotation should be placed in the given annotations UI.Parameters
uiName : string
The name of the annotations UI to activate.
filter : () => boolean
The annotation filter function. If not specified, the UI will use all annotations.
Defaults to
...
Returns
void
-
inherited
bind( bindProperties ) → MultiBindChain
module:comments/annotations/annotationsuis~AnnotationsUIs#bind:MANY_BIND
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 : Array<'off' | 'on' | 'once' | 'listenTo' | 'stopListening' | 'fire' | 'delegate' | 'stopDelegating' | 'set' | 'bind' | 'unbind' | 'decorate' | 'destroy' | 'context' | 'register' | 'init' | 'isActive' | 'deactivateAll' | 'activeUIs' | 'activate' | 'hasActive' | 'deactivate' | 'switchTo' | 'refilterAnnotations'>
Observable properties that will be bound to other observable(s).
Returns
MultiBindChain
The bind chain with the
to()
andtoMany()
methods.
-
inherited
bind( bindProperty1, bindProperty2 ) → DualBindChain<K1, AnnotationsUIs[ K1 ], K2, AnnotationsUIs[ K2 ]>
module:comments/annotations/annotationsuis~AnnotationsUIs#bind:DUAL_BIND
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 );
Type parameters
K1
K2
Parameters
bindProperty1 : K1
Observable property that will be bound to other observable(s).
bindProperty2 : K2
Observable property that will be bound to other observable(s).
Returns
DualBindChain<K1, AnnotationsUIs[ K1 ], K2, AnnotationsUIs[ K2 ]>
The bind chain with the
to()
andtoMany()
methods.
-
inherited
bind( bindProperty ) → SingleBindChain<K, AnnotationsUIs[ K ]>
module:comments/annotations/annotationsuis~AnnotationsUIs#bind:SINGLE_BIND
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 );
Type parameters
K
Parameters
bindProperty : K
Observable property that will be bound to other observable(s).
Returns
SingleBindChain<K, AnnotationsUIs[ K ]>
The bind chain with the
to()
andtoMany()
methods.
-
deactivate( uiName ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#deactivate
Deactivates annotations UI with given name.
Parameters
uiName : string
The name of the annotations UI to deactivate.
Returns
void
-
deactivateAll() → void
module:comments/annotations/annotationsuis~AnnotationsUIs#deactivateAll
Deactivates all annotations UIs.
Returns
void
-
inherited
decorate( methodName ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#decorate
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 extends ObservableMixin() { constructor() { super(); 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 : 'off' | 'on' | 'once' | 'listenTo' | 'stopListening' | 'fire' | 'delegate' | 'stopDelegating' | 'set' | 'bind' | 'unbind' | 'decorate' | 'destroy' | 'context' | 'register' | 'init' | 'isActive' | 'deactivateAll' | 'activeUIs' | 'activate' | 'hasActive' | 'deactivate' | 'switchTo' | 'refilterAnnotations'
Name of the method to decorate.
Returns
void
-
inherited
delegate( events ) → EmitterMixinDelegateChain
module:comments/annotations/annotationsuis~AnnotationsUIs#delegate
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 : Array<string>
Event names that will be delegated to another emitter.
Returns
-
destroy() → void
module:comments/annotations/annotationsuis~AnnotationsUIs#destroy
Destroys the plugin.
Note: This method is optional. A plugin instance does not need to have it defined.
Returns
void
-
inherited
fire( eventOrInfo, args ) → GetEventInfo<TEvent>[ 'return' ]
module:comments/annotations/annotationsuis~AnnotationsUIs#fire
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.Type parameters
Parameters
eventOrInfo : GetNameOrEventInfo<TEvent>
The name of the event or
EventInfo
object if event is delegated.args : TEvent[ 'args' ]
Additional arguments to be passed to the callbacks.
Returns
GetEventInfo<TEvent>[ 'return' ]
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).
-
hasActive() → boolean
module:comments/annotations/annotationsuis~AnnotationsUIs#hasActive
Returns
true
if at least one registered UI is active.Returns
boolean
-
init() → void
module:comments/annotations/annotationsuis~AnnotationsUIs#init
Returns
void
-
isActive( uiName ) → boolean
module:comments/annotations/annotationsuis~AnnotationsUIs#isActive
Returns
true
if the given UI is active.Parameters
uiName : string
Returns
boolean
-
inherited
listenTo( emitter, event, callback, [ options ] ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#listenTo:BASE_EMITTER
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.Type parameters
Parameters
emitter : Emitter
The object that fires the event.
event : TEvent[ 'name' ]
The name of the event.
callback : GetCallback<TEvent>
The function to be called on event.
[ options ] : GetCallbackOptions<TEvent>
Additional options.
Returns
void
-
inherited
off( event, callback ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#off
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.
Returns
void
-
inherited
on( event, callback, [ options ] ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#on
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).Type parameters
Parameters
event : TEvent[ 'name' ]
The name of the event.
callback : GetCallback<TEvent>
The function to be called on event.
[ options ] : GetCallbackOptions<TEvent>
Additional options.
Returns
void
-
inherited
once( event, callback, [ options ] ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#once
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.Type parameters
Parameters
event : TEvent[ 'name' ]
The name of the event.
callback : GetCallback<TEvent>
The function to be called on event.
[ options ] : GetCallbackOptions<TEvent>
Additional options.
Returns
void
-
refilterAnnotations() → void
module:comments/annotations/annotationsuis~AnnotationsUIs#refilterAnnotations
Refilters annotations to proper UIs based on filters provided earlier during the annotations UIs activation.
This method should be used if the annotations UIs filtering functions return different results than before for some annotations. It only reattaches these annotations, which should change their UIs.
Returns
void
-
register( uiName, annotationsUI ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#register
Registers an annotations UI. It might be one of:
It is possible to provide your own, custom annotations UI plugin. It has to implement the
AnnotationsUI
interface.Parameters
uiName : string
Annotations UI name.
annotationsUI : AnnotationsUI<Plugin | ContextPlugin>
Annotations UI plugin instance.
Returns
void
-
Creates and sets the value of an observable properties of this object. Such a property becomes a part of the state and is observable.
It accepts a single object literal containing key/value pairs with properties to be set.
This method throws the
observable-set-cannot-override
error if the observable instance already has a property with the given property name. This prevents from mistakenly overriding existing properties and methods, but means thatfoo.set( 'bar', 1 )
may be slightly slower thanfoo.bar = 1
.In TypeScript, those properties should be declared in class using
declare
keyword. In example:public declare myProp1: number; public declare myProp2: string; constructor() { this.set( { 'myProp1: 2, 'myProp2: 'foo' } ); }
Parameters
values : object
An object with
name=>value
pairs.
Returns
void
-
inherited
set( name, value ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#set:KEY_VALUE
Creates and sets the value of an observable property of this object. Such a property becomes a part of the state and is observable.
This method throws the
observable-set-cannot-override
error if the observable instance already has a property with the given property name. This prevents from mistakenly overriding existing properties and methods, but means thatfoo.set( 'bar', 1 )
may be slightly slower thanfoo.bar = 1
.In TypeScript, those properties should be declared in class using
declare
keyword. In example:public declare myProp: number; constructor() { this.set( 'myProp', 2 ); }
Type parameters
K
Parameters
name : K
The property's name.
value : AnnotationsUIs[ K ]
The property's value.
Returns
void
-
inherited
stopDelegating( [ event ], [ emitter ] ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#stopDelegating
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.
Returns
void
-
inherited
stopListening( [ emitter ], [ event ], [ callback ] ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#stopListening:BASE_STOP
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
.
Returns
void
-
switchTo( uiName ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#switchTo
Switches the annotations UI to the one with given name.
It preserves the currently active annotation.
Parameters
uiName : string
The name of the annotations UI to switch to.
Returns
void
-
inherited
unbind( unbindProperties ) → void
module:comments/annotations/annotationsuis~AnnotationsUIs#unbind
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 : Array<'off' | 'on' | 'once' | 'listenTo' | 'stopListening' | 'fire' | 'delegate' | 'stopDelegating' | 'set' | 'bind' | 'unbind' | 'decorate' | 'destroy' | 'context' | 'register' | 'init' | 'isActive' | 'deactivateAll' | 'activeUIs' | 'activate' | 'hasActive' | 'deactivate' | 'switchTo' | 'refilterAnnotations'>
Observable properties to be unbound. All the bindings will be released if no properties are provided.
Returns
void
Events
-
inherited
change:{property}( eventInfo, name, value, oldValue )
module:comments/annotations/annotationsuis~AnnotationsUIs#event:change:{property}
Fired when a property changed value.
observable.set( 'prop', 1 ); observable.on<ObservableChangeEvent<number>>( '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 : TValue
The new property value.
oldValue : TValue
The previous property value.
-
inherited
set:{property}( eventInfo, name, value, oldValue )
module:comments/annotations/annotationsuis~AnnotationsUIs#event:set:{property}
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<ObservableSetEvent<number>>( '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<ObservableChangeEvent<number>>( '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 : TValue
The new property value.
oldValue : TValue
The previous property value.
Every day, we work hard to keep our documentation complete. Have you spotted outdated information? Is something missing? Please report it via our issue tracker.
With the release of version 42.0.0, we have rewritten much of our documentation to reflect the new import paths and features. We appreciate your feedback to help us ensure its accuracy and completeness.