# CommentThread

class

Comment thread representation. Stores a list of [`Comments`](module_comments_comments_commentsrepository-Comment.md).

<a id="properties">

## Properties

<a id="member-archivedAt">

### `archivedAt: Date | null` _(observable)_

Date when the comment thread has been archived.

Comment threads become archived after they are [resolved](#member-resolvedAt) or [unlinked](#member-unlinkedAt). If the comment thread is resolved and/or unlinked, this value is set to the earliest of the dates. Otherwise, it is `null`.

<a id="member-attributes">

### `attributes: Record<string, unknown>` _(observable)_

Custom comment thread attributes. See also [`setAttribute`](#function-setAttribute) and [`removeAttribute`](#function-removeAttribute).

<a id="member-canComment">

### `canComment: boolean` _(observable)_

Informs if a user has permission to add a new comment to the comment thread.

<a id="member-channelId">

### `channelId: string | symbol`

The channel where the comment thread was created.

<a id="member-comments">

### `comments: Collection<Comment>` _(readonly)_

A collection of [`Comment`](module_comments_comments_commentsrepository-Comment.md)s belonging to this thread.

<a id="member-id">

### `id: string`

The comment thread ID.

<a id="member-isAttached">

### `isAttached: boolean` _(readonly)_

Informs if the comment thread is attached to any target at the moment.

<a id="member-isReadOnly">

### `isReadOnly: boolean` _(observable)_

Informs if the comment thread is in read-only state (`true`) or not (`false`).

<a id="member-isRemovable">

### `isRemovable: boolean` _(observable)_

Informs if the comment thread can be removed by the local user.

<a id="member-isResolved">

### `isResolved: boolean` _(readonly)_

Informs if the comment thread is resolved.

<a id="member-isSubmitted">

### `isSubmitted: boolean` _(readonly)_

Informs if the comment thread has been submitted.

<a id="member-length">

### `length: number` _(readonly)_

The number of [comments](module_comments_comments_commentsrepository-Comment.md) in the comment thread.

<a id="member-resolvedAt">

### `resolvedAt: Date | null` _(observable)_

Date when the comment thread has been resolved.

<a id="member-resolvedBy">

### `resolvedBy: User | null` _(observable)_

User id which resolved the comment thread.

<a id="member-unlinkedAt">

### `unlinkedAt: Date | null` _(observable)_

The date when the content related to the comment thread was lost (usually, the commented content was removed from the document).

<a id="member-weight">

### `weight: number` _(readonly)_

Sum of [weights of all comments](module_comments_comments_commentsrepository-Comment.md#member-weight) in this thread.

<a id="methods">

## Methods

<a id="function-constructor">

### `constructor( commentsRepository, data = { data.attributes, data.channelId, data.context, data.id, data.isResolvable, data.isSubmitted, data.resolvedAt, data.resolvedBy, data.unlinkedAt } )`

#### Parameters

* `commentsRepository: CommentsRepository`

* `data: object`

  Properties

  * `data.attributes: Record<string, unknown>`
  * `data.channelId: string | symbol`
  * `data.context: CommentThreadContext`
  * `data.id: string`
  * `data.isResolvable: boolean`
  * `data.isSubmitted: boolean`
  * `data.resolvedAt: Date | null`
  * `data.resolvedBy: User | null`
  * `data.unlinkedAt: Date | null`

<a id="function-addComment">

### `addComment( data ) → void`

Creates a new comment inside the comment thread.

**Note** This method is event-driven. It means it fires an event then a normal priority listener catches it and executes an action. It makes it possible to add some actions before and after method will be executed.

See also [`setAttribute`](module_comments_comments_commentsrepository-Comment.md#function-setAttribute) and [`removeAttribute`](module_comments_comments_commentsrepository-Comment.md#function-removeAttribute).

#### Parameters

* `data: CommentData`

  Data object.

#### Returns

* `void`

#### Fires

* [addComment](module_comments_comments_commentsrepository-CommentsRepository.md#event-addComment)

<a id="function-attachTo">

### `attachTo( target ) → Annotation`

Creates comment annotations and displays it attached to the given target.

#### Parameters

* `target: AnnotationTarget`

#### Returns

* `Annotation`

  Created annotation.

<a id="function-bind:DUAL_BIND">

### `bind( bindProperty1, bindProperty2 ) → ObservableDualBindChain<K1, CommentThread[ K1 ], K2, CommentThread[ K2 ]>` _(inherited)_

Binds [observable properties](#function-set:KEY_VALUE) to other objects implementing the [`Observable`](module_utils_observablemixin-Observable.md) interface.

Read more in the [dedicated](../framework/deep-dive/observables.md#property-bindings) guide covering the topic of property bindings with some additional examples.

Consider two objects: a `button` and an associated `command` (both `Observable`).

A simple property binding could be as follows:

```typescript
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
```

or even shorter:

```typescript
button.bind( 'isEnabled' ).to( command );
```

which works in the following way:

* `button.isEnabled` **instantly equals** `command.isEnabled`,
* whenever `command.isEnabled` changes, `button.isEnabled` will immediately reflect its value.

**Note**: To release the binding, use [`unbind`](module_utils_observablemixin-Observable.md#function-unbind).

You can also "rename" the property in the binding by specifying the new name in the `to()` chain:

```typescript
button.bind( 'isEnabled' ).to( command, 'isWorking' );
```

It is possible to bind more than one property at a time to shorten the code:

```typescript
button.bind( 'isEnabled', 'value' ).to( command );
```

which corresponds to:

```typescript
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:

```typescript
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:

```typescript
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 (also `Observables`) so that each and every one of them must be enabled for the button to become enabled, use the following code:

```typescript
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

* `ObservableDualBindChain<K1, CommentThread[ K1 ], K2, CommentThread[ K2 ]>`

  The bind chain with the `to()` and `toMany()` methods.

<a id="function-bind:MANY_BIND">

### `bind( bindProperties ) → ObservableMultiBindChain` _(inherited)_

Binds [observable properties](#function-set:KEY_VALUE) to other objects implementing the [`Observable`](module_utils_observablemixin-Observable.md) interface.

Read more in the [dedicated](../framework/deep-dive/observables.md#property-bindings) guide covering the topic of property bindings with some additional examples.

Consider two objects: a `button` and an associated `command` (both `Observable`).

A simple property binding could be as follows:

```typescript
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
```

or even shorter:

```typescript
button.bind( 'isEnabled' ).to( command );
```

which works in the following way:

* `button.isEnabled` **instantly equals** `command.isEnabled`,
* whenever `command.isEnabled` changes, `button.isEnabled` will immediately reflect its value.

**Note**: To release the binding, use [`unbind`](module_utils_observablemixin-Observable.md#function-unbind).

You can also "rename" the property in the binding by specifying the new name in the `to()` chain:

```typescript
button.bind( 'isEnabled' ).to( command, 'isWorking' );
```

It is possible to bind more than one property at a time to shorten the code:

```typescript
button.bind( 'isEnabled', 'value' ).to( command );
```

which corresponds to:

```typescript
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:

```typescript
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:

```typescript
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 (also `Observables`) so that each and every one of them must be enabled for the button to become enabled, use the following code:

```typescript
button.bind( 'isEnabled' ).toMany( [ commandA, commandB, commandC ], 'isEnabled',
	( isAEnabled, isBEnabled, isCEnabled ) => isAEnabled && isBEnabled && isCEnabled );
```

#### Parameters

* `bindProperties: Array<'length' | 'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'submit' | 'remove' | 'id' | 'attributes' | 'isReadOnly' | 'toJSON' | 'isAttached' | '_remove' | 'removeAttribute' | 'context' | '_isAttached' | 'setAttribute' | 'attachTo' | 'comments' | 'resolve' | 'isRemovable' | 'resolvedAt' | 'weight' | 'addComment' | 'canComment' | 'archivedAt' | 'unlinkedAt' | 'resolvedBy' | 'isResolved' | 'isResolvable' | '_hasTargetInContent' | 'channelId' | '_isSubmitted' | 'isSubmitted' | 'setUnlinkedAt' | 'reopen' | 'setContext' | 'getComment' | '_add' | '_update' | '_findOptimalIndex'>`

  Observable properties that will be bound to other observable(s).

#### Returns

* `ObservableMultiBindChain`

  The bind chain with the `to()` and `toMany()` methods.

<a id="function-bind:SINGLE_BIND">

### `bind( bindProperty ) → ObservableSingleBindChain<K, CommentThread[ K ]>` _(inherited)_

Binds [observable properties](#function-set:KEY_VALUE) to other objects implementing the [`Observable`](module_utils_observablemixin-Observable.md) interface.

Read more in the [dedicated](../framework/deep-dive/observables.md#property-bindings) guide covering the topic of property bindings with some additional examples.

Consider two objects: a `button` and an associated `command` (both `Observable`).

A simple property binding could be as follows:

```typescript
button.bind( 'isEnabled' ).to( command, 'isEnabled' );
```

or even shorter:

```typescript
button.bind( 'isEnabled' ).to( command );
```

which works in the following way:

* `button.isEnabled` **instantly equals** `command.isEnabled`,
* whenever `command.isEnabled` changes, `button.isEnabled` will immediately reflect its value.

**Note**: To release the binding, use [`unbind`](module_utils_observablemixin-Observable.md#function-unbind).

You can also "rename" the property in the binding by specifying the new name in the `to()` chain:

```typescript
button.bind( 'isEnabled' ).to( command, 'isWorking' );
```

It is possible to bind more than one property at a time to shorten the code:

```typescript
button.bind( 'isEnabled', 'value' ).to( command );
```

which corresponds to:

```typescript
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:

```typescript
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:

```typescript
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 (also `Observables`) so that each and every one of them must be enabled for the button to become enabled, use the following code:

```typescript
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

* `ObservableSingleBindChain<K, CommentThread[ K ]>`

  The bind chain with the `to()` and `toMany()` methods.

<a id="function-decorate">

### `decorate( methodName ) → void` _(inherited)_

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](../framework/deep-dive/observables.md#decorating-object-methods) 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](module_utils_eventinfo-EventInfo.md#member-stop):

```typescript
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](module_utils_priorities-PriorityString.md) 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:

```typescript
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:

```typescript
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: 'length' | 'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'submit' | 'remove' | 'id' | 'attributes' | 'isReadOnly' | 'toJSON' | 'isAttached' | '_remove' | 'removeAttribute' | 'context' | '_isAttached' | 'setAttribute' | 'attachTo' | 'comments' | 'resolve' | 'isRemovable' | 'resolvedAt' | 'weight' | 'addComment' | 'canComment' | 'archivedAt' | 'unlinkedAt' | 'resolvedBy' | 'isResolved' | 'isResolvable' | '_hasTargetInContent' | 'channelId' | '_isSubmitted' | 'isSubmitted' | 'setUnlinkedAt' | 'reopen' | 'setContext' | 'getComment' | '_add' | '_update' | '_findOptimalIndex'`

  Name of the method to decorate.

#### Returns

* `void`

<a id="function-delegate">

### `delegate( events ) → EmitterMixinDelegateChain` _(inherited)_

Delegates selected events to another [`Emitter`](module_utils_emittermixin-Emitter.md). For instance:

```typescript
emitterA.delegate( 'eventX' ).to( emitterB );
emitterA.delegate( 'eventX', 'eventY' ).to( emitterC );
```

then `eventX` is delegated (fired by) `emitterB` and `emitterC` along with `data`:

```typescript
emitterA.fire( 'eventX', data );
```

and `eventY` is delegated (fired by) `emitterC` along with `data`:

```typescript
emitterA.fire( 'eventY', data );
```

#### Parameters

* `events: Array<string>`

  Event names that will be delegated to another emitter.

#### Returns

* `EmitterMixinDelegateChain`

<a id="function-fire">

### `fire( eventOrInfo, args ) → GetEventInfo<TEvent>[ 'return' ]` _(inherited)_

Fires an event, executing all callbacks registered for it.

The first parameter passed to callbacks is an [`EventInfo`](module_utils_eventinfo-EventInfo.md) object, followed by the optional `args` provided in the `fire()` method call.

#### Type parameters

* `TEvent: extends BaseEvent`

  The type describing the event. See [`BaseEvent`](module_utils_emittermixin-BaseEvent.md).

#### 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 the [`evt.return`](module_utils_eventinfo-EventInfo.md#member-return)'s property (the event info is the first param of every callback).

<a id="function-getComment">

### `getComment( commentId ) → Comment | null`

Returns comment of given id.

#### Parameters

* `commentId: string`

#### Returns

* `Comment | null`

<a id="function-listenTo:BASE_EMITTER">

### `listenTo( emitter, event, callback, options? ) → void` _(inherited)_

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.

```typescript
// 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](module_utils_eventinfo-EventInfo.md#member-stop) and set the [return value](module_utils_eventinfo-EventInfo.md#member-return) of the [`fire`](#function-fire) method.

#### Type parameters

* `TEvent: extends BaseEvent`

  The type describing the event. See [`BaseEvent`](module_utils_emittermixin-BaseEvent.md).

#### 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`

<a id="function-off">

### `off( event, callback ) → void` _(inherited)_

Stops executing the callback on the given event. Shorthand for [`this.stopListening( this, event, callback )`](#function-stopListening:BASE_STOP).

#### Parameters

* `event: string`

  The name of the event.

* `callback: Function`

  The function to stop being called.

#### Returns

* `void`

<a id="function-on">

### `on( event, callback, options? ) → void` _(inherited)_

Registers a callback function to be executed when an event is fired.

Shorthand for [`this.listenTo( this, event, callback, options )`](#function-listenTo:BASE_EMITTER) (it makes the emitter listen on itself).

#### Type parameters

* `TEvent: extends BaseEvent`

  The type descibing the event. See [`BaseEvent`](module_utils_emittermixin-BaseEvent.md).

#### 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`

<a id="function-once">

### `once( event, callback, options? ) → void` _(inherited)_

Registers a callback function to be executed on the next time the event is fired only. This is similar to calling [`on`](#function-on) followed by [`off`](#function-off) in the callback.

#### Type parameters

* `TEvent: extends BaseEvent`

  The type descibing the event. See [`BaseEvent`](module_utils_emittermixin-BaseEvent.md).

#### 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`

<a id="function-remove">

### `remove( __namedParameters ) → void`

Removes comment thread.

**Note** This method is event-driven. It means it fires an event then a normal priority listener catches it and executes an action. It makes it possible to add some actions before and after method will be executed.

#### Parameters

* `__namedParameters: Pick<BaseCommentThread, 'isFromAdapter'>`

  Defaults to `{}`

#### Returns

* `void`

#### Fires

* [RemoveCommentThreadEvent](module_comments_comments_commentsrepository-RemoveCommentThreadEvent.md)

<a id="function-removeAttribute">

### `removeAttribute( name ) → void`

Removes a comment attribute.

See also [`setAttribute`](#function-setAttribute).

#### Parameters

* `name: string`

  The attribute name.

#### Returns

* `void`

#### Fires

* [updateCommentThread](module_comments_comments_commentsrepository-CommentsRepository.md#event-updateCommentThread)

<a id="function-reopen">

### `reopen( __namedParameters ) → void`

Reopens the resolved comment thread.

#### Parameters

* `__namedParameters: Pick<BaseCommentThread, 'isFromAdapter'>`

  Defaults to `{}`

#### Returns

* `void`

<a id="function-resolve">

### `resolve( __namedParameters ) → void`

Resolves the comment thread.

#### Parameters

* `__namedParameters: Partial<Pick<ResolveCommentThreadEventData, 'resolvedAt' | 'resolvedBy' | 'isFromAdapter'>>`

  Defaults to `{}`

#### Returns

* `void`

<a id="function-set:OBJECT">

### `set( values ) → void` _(inherited)_

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 that `foo.set( 'bar', 1 )` may be slightly slower than `foo.bar = 1`.

In TypeScript, those properties should be declared in class using `declare` keyword. In example:

```typescript
public declare myProp1: number;
public declare myProp2: string;

constructor() {
	this.set( {
		'myProp1: 2,
		'myProp2: 'foo'
	} );
}
```

#### Parameters

* `values: object & object`

  An object with `name=>value` pairs.

#### Returns

* `void`

<a id="function-set:KEY_VALUE">

### `set( name, value ) → void` _(inherited)_

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 that `foo.set( 'bar', 1 )` may be slightly slower than `foo.bar = 1`.

In TypeScript, those properties should be declared in class using `declare` keyword. In example:

```typescript
public declare myProp: number;

constructor() {
	this.set( 'myProp', 2 );
}
```

#### Type parameters

* `K`

#### Parameters

* `name: K`

  The property's name.

* `value: CommentThread[ K ]`

  The property's value.

#### Returns

* `void`

<a id="function-setAttribute">

### `setAttribute( name, value ) → void`

Adds attribute to the comment thread.

Comment thread attributes are custom data that can be set and used by features built around comments. Use it to store your feature data with other comment thread data. You can also group multiple values in an object, using dot notation:

```typescript
commentThread.setAttribute( 'customData.isImportant', true );
```

Attributes set on the comment can be accessed through the `attribute` property:

```typescript
const isImportant = commentThread.attributes.customData.isImportant;
```

You can also observe the `attributes` property or bind other properties to it:

```typescript
myObj.bind( 'customData' ).to( commentThread, 'attributes', attributes => attributes.customData );
```

Whenever `setAttribute()` or `removeAttribute()` is called, the `attributes` property is re-set and observables are refreshed.

#### Parameters

* `name: string`

  Attribute name.

* `value: unknown`

  Attribute value.

#### Returns

* `void`

#### Fires

* [updateCommentThread](module_comments_comments_commentsrepository-CommentsRepository.md#event-updateCommentThread)

<a id="function-setContext">

### `setContext( context ) → void`

Set the context on the comment thread. This method should be called only when the context has been not set during initialization.

#### Parameters

* `context: CommentThreadContext`

  Text context of comment thread.

#### Returns

* `void`

<a id="function-setUnlinkedAt">

### `setUnlinkedAt( unlinkedAt ) → void`

Updates the unlinked date.

#### Parameters

* `unlinkedAt: Date | null`

#### Returns

* `void`

<a id="function-stopDelegating">

### `stopDelegating( event?, emitter? ) → void` _(inherited)_

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 of `event` to all emitters.

#### Returns

* `void`

<a id="function-stopListening:BASE_STOP">

### `stopListening( emitter?, event?, callback? ) → void` _(inherited)_

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 from `emitter`.

* `callback?: Function`

  (Requires the `event`) The function to be removed from the call list for the given `event`.

#### Returns

* `void`

<a id="function-submit">

### `submit() → void`

Submits the locally created comment thread draft.

#### Returns

* `void`

<a id="function-toJSON">

### `toJSON() → CommentThreadDataJSON`

#### Returns

* `CommentThreadDataJSON`

<a id="function-unbind">

### `unbind( unbindProperties ) → void` _(inherited)_

Removes the binding created with [`bind`](#function-bind:SINGLE_BIND).

```typescript
// Removes the binding for the 'a' property.
A.unbind( 'a' );

// Removes bindings for all properties.
A.unbind();
```

#### Parameters

* `unbindProperties: Array<'length' | 'off' | 'set' | 'bind' | 'unbind' | 'decorate' | 'stopListening' | 'on' | 'once' | 'listenTo' | 'fire' | 'delegate' | 'stopDelegating' | 'submit' | 'remove' | 'id' | 'attributes' | 'isReadOnly' | 'toJSON' | 'isAttached' | '_remove' | 'removeAttribute' | 'context' | '_isAttached' | 'setAttribute' | 'attachTo' | 'comments' | 'resolve' | 'isRemovable' | 'resolvedAt' | 'weight' | 'addComment' | 'canComment' | 'archivedAt' | 'unlinkedAt' | 'resolvedBy' | 'isResolved' | 'isResolvable' | '_hasTargetInContent' | 'channelId' | '_isSubmitted' | 'isSubmitted' | 'setUnlinkedAt' | 'reopen' | 'setContext' | 'getComment' | '_add' | '_update' | '_findOptimalIndex'>`

  Observable properties to be unbound. All the bindings will be released if no properties are provided.

#### Returns

* `void`

<a id="events">

## Events

<a id="event-change:_hasTargetInContent">

### `change:_hasTargetInContent( eventInfo, name, value, oldValue )`

Fired when the `_hasTargetInContent` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`_hasTargetInContent`).

* `value: boolean`

  New value of the `_hasTargetInContent` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `_hasTargetInContent` property with given key or `null`, if property was not set before.

<a id="event-change:archivedAt">

### `change:archivedAt( eventInfo, name, value, oldValue )`

Fired when the `archivedAt` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`archivedAt`).

* `value: Date | null`

  New value of the `archivedAt` property with given key or `null`, if operation should remove property.

* `oldValue: Date | null`

  Old value of the `archivedAt` property with given key or `null`, if property was not set before.

<a id="event-change:attributes">

### `change:attributes( eventInfo, name, value, oldValue )`

Fired when the `attributes` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`attributes`).

* `value: Record<string, unknown>`

  New value of the `attributes` property with given key or `null`, if operation should remove property.

* `oldValue: Record<string, unknown>`

  Old value of the `attributes` property with given key or `null`, if property was not set before.

<a id="event-change:canComment">

### `change:canComment( eventInfo, name, value, oldValue )`

Fired when the `canComment` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`canComment`).

* `value: boolean`

  New value of the `canComment` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `canComment` property with given key or `null`, if property was not set before.

<a id="event-change:context">

### `change:context( eventInfo, name, value, oldValue )`

Fired when the `context` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`context`).

* `value: CommentThreadContext`

  New value of the `context` property with given key or `null`, if operation should remove property.

* `oldValue: CommentThreadContext`

  Old value of the `context` property with given key or `null`, if property was not set before.

<a id="event-change:isReadOnly">

### `change:isReadOnly( eventInfo, name, value, oldValue )`

Fired when the `isReadOnly` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isReadOnly`).

* `value: boolean`

  New value of the `isReadOnly` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isReadOnly` property with given key or `null`, if property was not set before.

<a id="event-change:isRemovable">

### `change:isRemovable( eventInfo, name, value, oldValue )`

Fired when the `isRemovable` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isRemovable`).

* `value: boolean`

  New value of the `isRemovable` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isRemovable` property with given key or `null`, if property was not set before.

<a id="event-change:isResolvable">

### `change:isResolvable( eventInfo, name, value, oldValue )`

Fired when the `isResolvable` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isResolvable`).

* `value: boolean`

  New value of the `isResolvable` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isResolvable` property with given key or `null`, if property was not set before.

<a id="event-change:isResolved">

### `change:isResolved( eventInfo, name, value, oldValue )`

Fired when the `isResolved` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isResolved`).

* `value: boolean`

  New value of the `isResolved` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isResolved` property with given key or `null`, if property was not set before.

<a id="event-change:resolvedAt">

### `change:resolvedAt( eventInfo, name, value, oldValue )`

Fired when the `resolvedAt` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`resolvedAt`).

* `value: Date | null`

  New value of the `resolvedAt` property with given key or `null`, if operation should remove property.

* `oldValue: Date | null`

  Old value of the `resolvedAt` property with given key or `null`, if property was not set before.

<a id="event-change:resolvedBy">

### `change:resolvedBy( eventInfo, name, value, oldValue )`

Fired when the `resolvedBy` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`resolvedBy`).

* `value: User | null`

  New value of the `resolvedBy` property with given key or `null`, if operation should remove property.

* `oldValue: User | null`

  Old value of the `resolvedBy` property with given key or `null`, if property was not set before.

<a id="event-change:unlinkedAt">

### `change:unlinkedAt( eventInfo, name, value, oldValue )`

Fired when the `unlinkedAt` property changed value.

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`unlinkedAt`).

* `value: Date | null`

  New value of the `unlinkedAt` property with given key or `null`, if operation should remove property.

* `oldValue: Date | null`

  Old value of the `unlinkedAt` property with given key or `null`, if property was not set before.

<a id="event-change:%7Bproperty%7D">

### `change:{property}( eventInfo, name, value, oldValue )` _(inherited)_

Fired when a property changed value.

```typescript
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.

<a id="event-set:_hasTargetInContent">

### `set:_hasTargetInContent( eventInfo, name, value, oldValue )`

Fired when the `_hasTargetInContent` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`_hasTargetInContent`).

* `value: boolean`

  New value of the `_hasTargetInContent` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `_hasTargetInContent` property with given key or `null`, if property was not set before.

<a id="event-set:archivedAt">

### `set:archivedAt( eventInfo, name, value, oldValue )`

Fired when the `archivedAt` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`archivedAt`).

* `value: Date | null`

  New value of the `archivedAt` property with given key or `null`, if operation should remove property.

* `oldValue: Date | null`

  Old value of the `archivedAt` property with given key or `null`, if property was not set before.

<a id="event-set:attributes">

### `set:attributes( eventInfo, name, value, oldValue )`

Fired when the `attributes` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`attributes`).

* `value: Record<string, unknown>`

  New value of the `attributes` property with given key or `null`, if operation should remove property.

* `oldValue: Record<string, unknown>`

  Old value of the `attributes` property with given key or `null`, if property was not set before.

<a id="event-set:canComment">

### `set:canComment( eventInfo, name, value, oldValue )`

Fired when the `canComment` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`canComment`).

* `value: boolean`

  New value of the `canComment` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `canComment` property with given key or `null`, if property was not set before.

<a id="event-set:context">

### `set:context( eventInfo, name, value, oldValue )`

Fired when the `context` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`context`).

* `value: CommentThreadContext`

  New value of the `context` property with given key or `null`, if operation should remove property.

* `oldValue: CommentThreadContext`

  Old value of the `context` property with given key or `null`, if property was not set before.

<a id="event-set:isReadOnly">

### `set:isReadOnly( eventInfo, name, value, oldValue )`

Fired when the `isReadOnly` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isReadOnly`).

* `value: boolean`

  New value of the `isReadOnly` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isReadOnly` property with given key or `null`, if property was not set before.

<a id="event-set:isRemovable">

### `set:isRemovable( eventInfo, name, value, oldValue )`

Fired when the `isRemovable` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isRemovable`).

* `value: boolean`

  New value of the `isRemovable` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isRemovable` property with given key or `null`, if property was not set before.

<a id="event-set:isResolvable">

### `set:isResolvable( eventInfo, name, value, oldValue )`

Fired when the `isResolvable` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isResolvable`).

* `value: boolean`

  New value of the `isResolvable` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isResolvable` property with given key or `null`, if property was not set before.

<a id="event-set:isResolved">

### `set:isResolved( eventInfo, name, value, oldValue )`

Fired when the `isResolved` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`isResolved`).

* `value: boolean`

  New value of the `isResolved` property with given key or `null`, if operation should remove property.

* `oldValue: boolean`

  Old value of the `isResolved` property with given key or `null`, if property was not set before.

<a id="event-set:resolvedAt">

### `set:resolvedAt( eventInfo, name, value, oldValue )`

Fired when the `resolvedAt` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`resolvedAt`).

* `value: Date | null`

  New value of the `resolvedAt` property with given key or `null`, if operation should remove property.

* `oldValue: Date | null`

  Old value of the `resolvedAt` property with given key or `null`, if property was not set before.

<a id="event-set:resolvedBy">

### `set:resolvedBy( eventInfo, name, value, oldValue )`

Fired when the `resolvedBy` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`resolvedBy`).

* `value: User | null`

  New value of the `resolvedBy` property with given key or `null`, if operation should remove property.

* `oldValue: User | null`

  Old value of the `resolvedBy` property with given key or `null`, if property was not set before.

<a id="event-set:unlinkedAt">

### `set:unlinkedAt( eventInfo, name, value, oldValue )`

Fired when the `unlinkedAt` property is going to be set but is not set yet (before the `change` event is fired).

#### Parameters

* `eventInfo: EventInfo`

  An object containing information about the fired event.

* `name: string`

  Name of the changed property (`unlinkedAt`).

* `value: Date | null`

  New value of the `unlinkedAt` property with given key or `null`, if operation should remove property.

* `oldValue: Date | null`

  Old value of the `unlinkedAt` property with given key or `null`, if property was not set before.

<a id="event-set:%7Bproperty%7D">

### `set:{property}( eventInfo, name, value, oldValue )` _(inherited)_

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](module_utils_eventinfo-EventInfo.md#member-return).

```typescript
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.

---

Full index of the CKEditor 5 API reference: [llms.txt](llms.txt)