CommentsRepository
Stores the list of CommentThread and provides event-driven API for managing them. It is also responsible for using the comments adapter to communicate with the data source.
CommentsRepository is a context plugin. It can be added to a context or to an editor. Add it to the context configuration if you use Context in your integration.
The event-driven API makes it possible to attach a listener to each action that changes comment data. Using different event priorities allows to attach an action before the main action ('low' priority) or after the main action ('high' priority). It works very similar to decorate.
Sample usage:
// Get the comments repository:
const commentsRepository = editor.plugins.get( 'CommentsRepository' );
// Create a new, empty comment thread on a DOM form field element:
commentsRepository.openNewCommentThread( { channelId, target: formFieldElement } );
// Get all comment threads:
commentsRepository.getCommentThreads();
// Set the adapter:
commentsRepository.adapter = {
// ...
};
For more information about the comments adapter see CommentsAdapter.
Properties
activeCommentThread : null | CommentThreadmodule:comments/comments/commentsrepository~CommentsRepository#activeCommentThreadThe currently active comment thread. An annotation with this thread will be marked as active.
module:comments/comments/commentsrepository~CommentsRepository#adapterParameters
adapter : CommentsAdapter
context : ContextInterfacereadonlyinheritedmodule:comments/comments/commentsrepository~CommentsRepository#contextThe context or editor instance.
Static properties
isContextPlugin : truereadonlyinheritedstaticmodule:comments/comments/commentsrepository~CommentsRepository.isContextPluginisOfficialPlugin : truereadonlystaticmodule:comments/comments/commentsrepository~CommentsRepository.isOfficialPluginisPremiumPlugin : truereadonlystaticmodule:comments/comments/commentsrepository~CommentsRepository.isPremiumPluginpluginName : 'CommentsRepository'readonlystaticmodule:comments/comments/commentsrepository~CommentsRepository.pluginNamerequires : readonly tuplereadonlystaticmodule:comments/comments/commentsrepository~CommentsRepository.requires
Methods
constructor( context )module:comments/comments/commentsrepository~CommentsRepository#constructoraddCommentThread( data ) → undefined | CommentThreadmodule:comments/comments/commentsrepository~CommentsRepository#addCommentThreadAdds a new comment thread.
When a target is provided, the comment annotation will be attached to this target.
Use this method to load the comments data during the editor initialization if you do not use the adapter integration.
Note: This method fires the event-addCommentThread event and the default behavior is added as a
'normal'priority listener. It makes it possible to cancel the method or call some custom code before or after the default behavior is executed.Note: The comments adapter will send the data only if
commentThreadData.commentsis not empty andcommentThreadData.isFromAdapteris set tofalse.See also
CommentsRepository#openNewCommentThread().An example of loading a comment thread on editor initialization:
commentsRepository.addCommentThread( { threadId: 'thread-id', channelId: 'channel-id', comments: [ { commentId: 'comment-1', // String authorId: 'author-id', // String content: 'First comment', // String createdAt: new Date( ... ) // Date instance }, // ... ], target: () => ..., // Added during initialization, so do not call the adapter: isFromAdapter: true } );Copy codeSee also
setAttributeandremoveAttribute.Parameters
data : Partial<AddCommentThreadEventData>The data of the comment thread to add.
Defaults to
...
Returns
undefined | CommentThreadThe added comment thread.
Fires
bind( bindProperties ) → ObservableMultiBindChaininheritedmodule:comments/comments/commentsrepository~CommentsRepository#bind:MANY_BINDBinds observable properties to other objects implementing the
Observableinterface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
buttonand an associatedcommand(bothObservable).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );Copy codeor even shorter:
button.bind( 'isEnabled' ).to( command );Copy codewhich works in the following way:
button.isEnabledinstantly equalscommand.isEnabled,- whenever
command.isEnabledchanges,button.isEnabledwill 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' );Copy codeIt is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );Copy codewhich corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );Copy codeThe 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 );Copy codeUsing a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );Copy codeIt is also possible to bind to the same property in an array of observables. To bind a
buttonto 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 );Copy codeParameters
bindProperties : Array<'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'destroy' | 'isReadOnly' | 'context' | 'init' | 'adapter' | '_permissions' | 'activeCommentThread' | '_adapter' | '_threads' | '_threadToController' | '_viewToController' | '_readOnlyChannels' | 'setPermissions' | 'addCommentThread' | 'openNewCommentThread' | 'hasCommentThread' | 'updateCommentThread' | 'getCommentThread' | 'fetchCommentThread' | 'getCommentThreads' | 'getAnnotationForCommentThread' | 'getCommentThreadForAnnotation' | 'setActiveCommentThread' | 'switchReadOnly' | 'createCommentThreadController' | 'getPermissions' | '_attachCommentThread' | '_bindAnnotationToEditors' | '_unbindEditors' | '_removeCommentThread' | '_detachCommentThread' | '_updateComment' | '_removeComment'>Observable properties that will be bound to other observable(s).
Returns
ObservableMultiBindChainThe bind chain with the
to()andtoMany()methods.
bind( bindProperty1, bindProperty2 ) → ObservableDualBindChain<K1, CommentsRepository[ K1 ], K2, CommentsRepository[ K2 ]>inheritedmodule:comments/comments/commentsrepository~CommentsRepository#bind:DUAL_BINDBinds observable properties to other objects implementing the
Observableinterface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
buttonand an associatedcommand(bothObservable).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );Copy codeor even shorter:
button.bind( 'isEnabled' ).to( command );Copy codewhich works in the following way:
button.isEnabledinstantly equalscommand.isEnabled,- whenever
command.isEnabledchanges,button.isEnabledwill 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' );Copy codeIt is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );Copy codewhich corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );Copy codeThe 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 );Copy codeUsing a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );Copy codeIt is also possible to bind to the same property in an array of observables. To bind a
buttonto 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 );Copy codeType parameters
K1K2
Parameters
bindProperty1 : K1Observable property that will be bound to other observable(s).
bindProperty2 : K2Observable property that will be bound to other observable(s).
Returns
ObservableDualBindChain<K1, CommentsRepository[ K1 ], K2, CommentsRepository[ K2 ]>The bind chain with the
to()andtoMany()methods.
bind( bindProperty ) → ObservableSingleBindChain<K, CommentsRepository[ K ]>inheritedmodule:comments/comments/commentsrepository~CommentsRepository#bind:SINGLE_BINDBinds observable properties to other objects implementing the
Observableinterface.Read more in the dedicated guide covering the topic of property bindings with some additional examples.
Consider two objects: a
buttonand an associatedcommand(bothObservable).A simple property binding could be as follows:
button.bind( 'isEnabled' ).to( command, 'isEnabled' );Copy codeor even shorter:
button.bind( 'isEnabled' ).to( command );Copy codewhich works in the following way:
button.isEnabledinstantly equalscommand.isEnabled,- whenever
command.isEnabledchanges,button.isEnabledwill 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' );Copy codeIt is possible to bind more than one property at a time to shorten the code:
button.bind( 'isEnabled', 'value' ).to( command );Copy codewhich corresponds to:
button.bind( 'isEnabled' ).to( command ); button.bind( 'value' ).to( command );Copy codeThe 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 );Copy codeUsing a custom callback allows processing the value before passing it to the target property:
button.bind( 'isEnabled' ).to( command, 'value', value => value === 'heading1' );Copy codeIt is also possible to bind to the same property in an array of observables. To bind a
buttonto 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 );Copy codeType parameters
K
Parameters
bindProperty : KObservable property that will be bound to other observable(s).
Returns
ObservableSingleBindChain<K, CommentsRepository[ K ]>The bind chain with the
to()andtoMany()methods.
createCommentThreadController( commentThreadModel, commentThreadView ) → CommentThreadControllermodule:comments/comments/commentsrepository~CommentsRepository#createCommentThreadControllerCreate an instance of the
CommentThreadControllerclass.Parameters
commentThreadModel : CommentThreadComment thread model.
commentThreadView : BaseCommentThreadViewComment thread view.
Returns
decorate( methodName ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#decorateTurns 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.Copy codeNote: 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'Copy codeFinally, 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'Copy codeParameters
methodName : 'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'destroy' | 'isReadOnly' | 'context' | 'init' | 'adapter' | '_permissions' | 'activeCommentThread' | '_adapter' | '_threads' | '_threadToController' | '_viewToController' | '_readOnlyChannels' | 'setPermissions' | 'addCommentThread' | 'openNewCommentThread' | 'hasCommentThread' | 'updateCommentThread' | 'getCommentThread' | 'fetchCommentThread' | 'getCommentThreads' | 'getAnnotationForCommentThread' | 'getCommentThreadForAnnotation' | 'setActiveCommentThread' | 'switchReadOnly' | 'createCommentThreadController' | 'getPermissions' | '_attachCommentThread' | '_bindAnnotationToEditors' | '_unbindEditors' | '_removeCommentThread' | '_detachCommentThread' | '_updateComment' | '_removeComment'Name of the method to decorate.
Returns
void
delegate( events ) → EmitterMixinDelegateChaininheritedmodule:comments/comments/commentsrepository~CommentsRepository#delegateDelegates selected events to another
Emitter. For instance:emitterA.delegate( 'eventX' ).to( emitterB ); emitterA.delegate( 'eventX', 'eventY' ).to( emitterC );Copy codethen
eventXis delegated (fired by)emitterBandemitterCalong withdata:emitterA.fire( 'eventX', data );Copy codeand
eventYis delegated (fired by)emitterCalong withdata:emitterA.fire( 'eventY', data );Copy codeParameters
events : Array<string>Event names that will be delegated to another emitter.
Returns
destroy() → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#destroyDestroys the plugin.
Note: This method is optional. A plugin instance does not need to have it defined.
Returns
void
fetchCommentThread( __namedParameters ) → Promise<undefined | CommentThread>module:comments/comments/commentsrepository~CommentsRepository#fetchCommentThreadGets the comment thread data using the adapter and adds the thread to the editor.
When the comment thread is already present in the repository, then the adapter will not be used but the result will be asynchronous as well.
Parameters
__namedParameters : BaseCommentThreadDefaults to
...
Returns
Promise<undefined | CommentThread>
fire( eventOrInfo, args ) → GetEventInfo<TEvent>[ 'return' ]inheritedmodule:comments/comments/commentsrepository~CommentsRepository#fireFires an event, executing all callbacks registered for it.
The first parameter passed to callbacks is an
EventInfoobject, followed by the optionalargsprovided in thefire()method call.Type parameters
Parameters
eventOrInfo : GetNameOrEventInfo<TEvent>The name of the event or
EventInfoobject 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).
getAnnotationForCommentThread( thread ) → null | Annotationmodule:comments/comments/commentsrepository~CommentsRepository#getAnnotationForCommentThreadReturns the annotation associated with the given comment thread.
Parameters
thread : CommentThread
Returns
null | Annotation
getCommentThread( threadId ) → undefined | CommentThreadmodule:comments/comments/commentsrepository~CommentsRepository#getCommentThreadgetCommentThreadForAnnotation( annotation ) → null | CommentThreadmodule:comments/comments/commentsrepository~CommentsRepository#getCommentThreadForAnnotationReturns the comment thread associated with the given annotation.
Parameters
annotation : Annotation
Returns
null | CommentThread
getCommentThreads( data = { [data.channelId], [data.skipEmpty], [data.skipNotAttached], data.toJSON } ) → Array<CommentThreadDataJSON>module:comments/comments/commentsrepository~CommentsRepository#getCommentThreadsParameters
data : object- Properties
[ data.channelId ] : string | symbol[ data.skipEmpty ] : boolean[ data.skipNotAttached ] : booleandata.toJSON : true
Returns
Array<CommentThreadDataJSON>
getCommentThreads( [ data ] = { [data.channelId], [data.skipEmpty], [data.skipNotAttached], [data.toJSON] } ) → Array<CommentThread>module:comments/comments/commentsrepository~CommentsRepository#getCommentThreadsParameters
[ data ] : object- Properties
[ data.channelId ] : string | symbol[ data.skipEmpty ] : boolean[ data.skipNotAttached ] : boolean[ data.toJSON ] : false
Returns
Array<CommentThread>
getPermissions( channelId ) → CommentPermissionsConfigmodule:comments/comments/commentsrepository~CommentsRepository#getPermissionsGets permissions set for repository (or default if permissions was not set).
Parameters
channelId : string | symbolDefaults to
noChannel
Returns
hasCommentThread( threadId ) → booleanmodule:comments/comments/commentsrepository~CommentsRepository#hasCommentThreadChecks if a comment thread with a given ID is added to the repository.
Parameters
threadId : string
Returns
boolean
init() → voidmodule:comments/comments/commentsrepository~CommentsRepository#initReturns
void
isReadOnly( channelId ) → booleanmodule:comments/comments/commentsrepository~CommentsRepository#isReadOnlyReturns
trueif a given channel is set to read-only mode, returnsfalseotherwise.Parameters
channelId : string | symbol
Returns
boolean
listenTo( emitter, event, callback, [ options ] ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#listenTo:BASE_EMITTERRegisters 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' );Copy codeAn event callback can stop the event and set the return value of the
firemethod.Type parameters
Parameters
emitter : EmitterThe 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
off( event, callback ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#offStops executing the callback on the given event. Shorthand for
this.stopListening( this, event, callback ).Parameters
event : stringThe name of the event.
callback : FunctionThe function to stop being called.
Returns
void
on( event, callback, [ options ] ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#onRegisters 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
once( event, callback, [ options ] ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#onceRegisters a callback function to be executed on the next time the event is fired only. This is similar to calling
onfollowed byoffin 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
openNewCommentThread( commentThreadData ) → null | CommentThreadmodule:comments/comments/commentsrepository~CommentsRepository#openNewCommentThreadCreates a new, empty comment thread.
Displays a new comment annotation attached to the target and focuses the comment editor. When the comment data is submitted, the comment thread is added to the editor and sent to the adapter.
Use this method to start a new comment thread after a user performed an action (clicked a button, etc.).
Parameters
commentThreadData : AddCommentThreadEventDataThe data of the comment thread to add.
Returns
null | CommentThreadThe created comment thread or
nullif there was a problem creating the thread (for example, if the comments repository was in the read-only mode).
Fires
set( values ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#set:OBJECTCreates 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-overrideerror 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
declarekeyword. In example:public declare myProp1: number; public declare myProp2: string; constructor() { this.set( { 'myProp1: 2, 'myProp2: 'foo' } ); }Copy codeParameters
values : objectAn object with
name=>valuepairs.
Returns
void
set( name, value ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#set:KEY_VALUECreates 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-overrideerror 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
declarekeyword. In example:public declare myProp: number; constructor() { this.set( 'myProp', 2 ); }Copy codeType parameters
K
Parameters
name : KThe property's name.
value : CommentsRepository[ K ]The property's value.
Returns
void
setActiveCommentThread( threadId ) → voidmodule:comments/comments/commentsrepository~CommentsRepository#setActiveCommentThreadMarks a comment thread with the given ID as active. When
threadIdisnull, the currently active comment thread will be deactivated.Parameters
threadId : null | string
Returns
void
stopDelegating( [ event ], [ emitter ] ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#stopDelegatingStops 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 ] : stringThe 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 ofeventto all emitters.
Returns
void
stopListening( [ emitter ], [ event ], [ callback ] ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#stopListening:BASE_STOPStops 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 ] : EmitterThe 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
switchReadOnly( value, [ channelId ] ) → voidmodule:comments/comments/commentsrepository~CommentsRepository#switchReadOnlyChanges the read-only state for comment threads.
When the value is
truethen all comment threads will be switched to read-only, when the value isfalsethen all comment threads will be switched to editing mode.Optionally new state can be applied to a comment threads limited to a given channel. This function has precedence over any permission settings.
Parameters
value : boolean[ channelId ] : string | symbol
Returns
void
unbind( unbindProperties ) → voidinheritedmodule:comments/comments/commentsrepository~CommentsRepository#unbindRemoves the binding created with
bind.// Removes the binding for the 'a' property. A.unbind( 'a' ); // Removes bindings for all properties. A.unbind();Copy codeParameters
unbindProperties : Array<'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'destroy' | 'isReadOnly' | 'context' | 'init' | 'adapter' | '_permissions' | 'activeCommentThread' | '_adapter' | '_threads' | '_threadToController' | '_viewToController' | '_readOnlyChannels' | 'setPermissions' | 'addCommentThread' | 'openNewCommentThread' | 'hasCommentThread' | 'updateCommentThread' | 'getCommentThread' | 'fetchCommentThread' | 'getCommentThreads' | 'getAnnotationForCommentThread' | 'getCommentThreadForAnnotation' | 'setActiveCommentThread' | 'switchReadOnly' | 'createCommentThreadController' | 'getPermissions' | '_attachCommentThread' | '_bindAnnotationToEditors' | '_unbindEditors' | '_removeCommentThread' | '_detachCommentThread' | '_updateComment' | '_removeComment'>Observable properties to be unbound. All the bindings will be released if no properties are provided.
Returns
void
updateCommentThread( data ) → CommentThreadmodule:comments/comments/commentsrepository~CommentsRepository#updateCommentThreadUpdates an existing comment thread. See also
setAttributeandremoveAttribute.Parameters
data : UpdateCommentThreadEventDataThe data of the comment thread to add.
Returns
CommentThreadThe updated comment thread.
Fires
Events
addComment( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:addCommentFired whenever a comment is added.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.It is also possible to listen to events from the given thread ID by appending
:[threadId]part to the event nameconst channelId = 'foo'; const threadId = '1234'; commentsRepository.on( `addComment:${ channelId }:${ threadId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : CommentEventData
addCommentThread( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:addCommentThreadFired whenever a comment thread is added to the comments repository.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.const channelId = 'foo'; commentsRepository.on( `addCommentThread:${ channelId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : Required<AddCommentThreadEventData>
change:_readOnlyChannels( eventInfo, name, value, oldValue )module:comments/comments/commentsrepository~CommentsRepository#event:change:_readOnlyChannelsFired when the
_readOnlyChannelsproperty changed value.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
_readOnlyChannels).value : Set<undefined | string | symbol>New value of the
_readOnlyChannelsproperty with given key ornull, if operation should remove property.oldValue : Set<undefined | string | symbol>Old value of the
_readOnlyChannelsproperty with given key ornull, if property was not set before.
change:activeCommentThread( eventInfo, name, value, oldValue )module:comments/comments/commentsrepository~CommentsRepository#event:change:activeCommentThreadFired when the
activeCommentThreadproperty changed value.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
activeCommentThread).value : null | CommentThreadNew value of the
activeCommentThreadproperty with given key ornull, if operation should remove property.oldValue : null | CommentThreadOld value of the
activeCommentThreadproperty with given key ornull, if property was not set before.
change:{property}( eventInfo, name, value, oldValue )inheritedmodule:comments/comments/commentsrepository~CommentsRepository#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'Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringThe property name.
value : TValueThe new property value.
oldValue : TValueThe previous property value.
removeComment( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:removeCommentFired whenever a comment is removed.
The event name includes
channelIdso it is possible to listen only to changes happening in the specified channel.It is also possible to listen to events from the given thread ID by appending
:[threadId]part to the event nameconst channelId = 'foo'; const threadId = '1234'; commentsRepository.on( `removeComment:${ channelId }:${ threadId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : BaseComment
removeCommentThread( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:removeCommentThreadFired whenever a comment thread is removed from the comments repository.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.const channelId = 'foo'; commentsRepository.on( `removeCommentThread:${ channelId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : BaseCommentThread
reopenCommentThread( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:reopenCommentThreadFired whenever a comment thread is reopened.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.const channelId = 'foo'; commentsRepository.on( `reopenCommentThread:${ channelId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : BaseCommentThread
resolveCommentThread( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:resolveCommentThreadFired whenever a comment thread is resolved.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.const channelId = 'foo'; commentsRepository.on( `resolveCommentThread:${ channelId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : ResolveCommentThreadEventData
set:_readOnlyChannels( eventInfo, name, value, oldValue )module:comments/comments/commentsrepository~CommentsRepository#event:set:_readOnlyChannelsFired when the
_readOnlyChannelsproperty is going to be set but is not set yet (before thechangeevent is fired).Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
_readOnlyChannels).value : Set<undefined | string | symbol>New value of the
_readOnlyChannelsproperty with given key ornull, if operation should remove property.oldValue : Set<undefined | string | symbol>Old value of the
_readOnlyChannelsproperty with given key ornull, if property was not set before.
set:activeCommentThread( eventInfo, name, value, oldValue )module:comments/comments/commentsrepository~CommentsRepository#event:set:activeCommentThreadFired when the
activeCommentThreadproperty is going to be set but is not set yet (before thechangeevent is fired).Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
activeCommentThread).value : null | CommentThreadNew value of the
activeCommentThreadproperty with given key ornull, if operation should remove property.oldValue : null | CommentThreadOld value of the
activeCommentThreadproperty with given key ornull, if property was not set before.
set:{property}( eventInfo, name, value, oldValue )inheritedmodule:comments/comments/commentsrepository~CommentsRepository#event:set:{property}Fired when a property value is going to be set but is not set yet (before the
changeevent is fired).You can control the final value of the property by using the event's
returnproperty.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'Copy codeNote: The event is fired even when the new value is the same as the old value.
Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringThe property name.
value : TValueThe new property value.
oldValue : TValueThe previous property value.
submitCommentThread( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:submitCommentThreadFired whenever a new comment thread is submitted and occurs after creating the first comment.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.const channelId = 'foo'; commentsRepository.on( `submitCommentThread:${ channelId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : BaseCommentThread
updateComment( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:updateCommentFired whenever a comment is updated.
The event name includes
channelIdso it is possible to listen only to changes happening in the specified channel.It is also possible to listen to events from the given thread ID by appending
:[threadId]part to the event nameconst channelId = 'foo'; const threadId = '1234'; commentsRepository.on( `updateComment:${ channelId }:${ threadId }`, ( evt, data ) => { console.log( evt, data ); } );Copy codeParameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : UpdateCommentEventData
updateCommentThread( eventInfo, <anonymous> )module:comments/comments/commentsrepository~CommentsRepository#event:updateCommentThreadFired whenever a comment thread is updated in comments repository.
The event name includes
channelIdso it is possible to listen only on changes happening in the specified channel.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
<anonymous> : UpdateCommentThreadEventData