RevisionTracker
Creates and updates revisions based on changes of the editor content.
There are always at least two revisions available for the document: the initial revision and the current revision. If those revisions have not been created for the document yet, they are created when the editor data is loaded.
The initial revision contains the initial document data from when the document was loaded for the first time.
The current revision contains all the unsaved document changes, that is changes which have not been saved yet as a specific revision. The current revision is always available and it is always the "top" revision (most recent).
Properties
currentRevision : null | Revisionmodule:revision-history/revisiontracker~RevisionTracker#currentRevisionThe revision instance that is used as a special "current revision", that is a revision that gathers all changes that have happened since the latest revision was saved.
module:revision-history/revisiontracker~RevisionTracker#editorThe editor instance.
Note that most editors implement the
uiproperty. However, editors with an external UI (i.e. Bootstrap-based) or a headless editor may not have this property or throw an error when accessing it.Because of above, to make plugins more universal, it is recommended to split features into:
module:revision-history/revisiontracker~RevisionTracker#repositoryRevisionsRepositoryplugin instance, holds revisions managed byRevisionTracker.
Static properties
isContextPlugin : falsereadonlyinheritedstaticmodule:revision-history/revisiontracker~RevisionTracker.isContextPluginpluginName : 'RevisionTracker'readonlystaticmodule:revision-history/revisiontracker~RevisionTracker.pluginNamerequires : readonly tuplereadonlystaticmodule:revision-history/revisiontracker~RevisionTracker.requires
Methods
constructor( editor )module:revision-history/revisiontracker~RevisionTracker#constructorParameters
editor : Editor
addRevisionData( revisionData ) → Revisionmodule:revision-history/revisiontracker~RevisionTracker#addRevisionDataCreates a revision basing on given revision data and adds it to the revision tracker and revision repository.
Parameters
revisionData : RevisionData
Returns
afterInit() → Promise<void>module:revision-history/revisiontracker~RevisionTracker#afterInitReturns
Promise<void>
bind( bindProperty1, bindProperty2 ) → ObservableDualBindChain<K1, RevisionTracker[ K1 ], K2, RevisionTracker[ K2 ]>inheritedmodule:revision-history/revisiontracker~RevisionTracker#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, RevisionTracker[ K1 ], K2, RevisionTracker[ K2 ]>The bind chain with the
to()andtoMany()methods.
bind( bindProperties ) → ObservableMultiBindChaininheritedmodule:revision-history/revisiontracker~RevisionTracker#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' | 'update' | 'init' | 'isEnabled' | 'licenseKey' | 'editor' | 'isReady' | 'forceDisabled' | 'clearForceDisabled' | 'afterInit' | 'adapter' | 'addRevisionData' | 'getRevisionDocumentData' | 'getRevisionRootsAttributes' | 'currentRevision' | 'repository' | '_revisionDataBuilder' | '_bufferedUpdates' | '_startingVersion' | '_isPendingUpdate' | 'saveRevision' | 'setSource' | 'sendBufferedUpdates' | 'buildRevisionData' | '_bufferUpdate' | 'setRevisionData' | '_createInitialRevision' | '_createCurrentRevision'>Observable properties that will be bound to other observable(s).
Returns
ObservableMultiBindChainThe bind chain with the
to()andtoMany()methods.
bind( bindProperty ) → ObservableSingleBindChain<K, RevisionTracker[ K ]>inheritedmodule:revision-history/revisiontracker~RevisionTracker#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, RevisionTracker[ K ]>The bind chain with the
to()andtoMany()methods.
clearForceDisabled( id ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#clearForceDisabledClears forced disable previously set through
forceDisabled. SeeforceDisabled.Parameters
id : stringUnique identifier, equal to the one passed in
forceDisabledcall.
Returns
void
decorate( methodName ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#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' | 'update' | 'init' | 'isEnabled' | 'licenseKey' | 'editor' | 'isReady' | 'forceDisabled' | 'clearForceDisabled' | 'afterInit' | 'adapter' | 'addRevisionData' | 'getRevisionDocumentData' | 'getRevisionRootsAttributes' | 'currentRevision' | 'repository' | '_revisionDataBuilder' | '_bufferedUpdates' | '_startingVersion' | '_isPendingUpdate' | 'saveRevision' | 'setSource' | 'sendBufferedUpdates' | 'buildRevisionData' | '_bufferUpdate' | 'setRevisionData' | '_createInitialRevision' | '_createCurrentRevision'Name of the method to decorate.
Returns
void
delegate( events ) → EmitterMixinDelegateChaininheritedmodule:revision-history/revisiontracker~RevisionTracker#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() → voidmodule:revision-history/revisiontracker~RevisionTracker#destroyDestroys the plugin.
Note: This method is optional. A plugin instance does not need to have it defined.
Returns
void
fire( eventOrInfo, args ) → GetEventInfo<TEvent>[ 'return' ]inheritedmodule:revision-history/revisiontracker~RevisionTracker#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
TEvent : extends BaseEventThe type describing the event. See
BaseEvent.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).
forceDisabled( id ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#forceDisabledDisables the plugin.
Plugin may be disabled by multiple features or algorithms (at once). When disabling a plugin, unique id should be passed (e.g. feature name). The same identifier should be used when enabling back the plugin. The plugin becomes enabled only after all features enabled it back.
Disabling and enabling a plugin:
plugin.isEnabled; // -> true plugin.forceDisabled( 'MyFeature' ); plugin.isEnabled; // -> false plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> trueCopy codePlugin disabled by multiple features:
plugin.forceDisabled( 'MyFeature' ); plugin.forceDisabled( 'OtherFeature' ); plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> false plugin.clearForceDisabled( 'OtherFeature' ); plugin.isEnabled; // -> trueCopy codeMultiple disabling with the same identifier is redundant:
plugin.forceDisabled( 'MyFeature' ); plugin.forceDisabled( 'MyFeature' ); plugin.clearForceDisabled( 'MyFeature' ); plugin.isEnabled; // -> trueCopy codeNote: some plugins or algorithms may have more complex logic when it comes to enabling or disabling certain plugins, so the plugin might be still disabled after
clearForceDisabledwas used.Parameters
id : stringUnique identifier for disabling. Use the same id when enabling back the plugin.
Returns
void
getRevisionDocumentData( revision ) → Promise<Record<string, string>>module:revision-history/revisiontracker~RevisionTracker#getRevisionDocumentDataReturns document data for given revision.
The document data is HTML or a different format, depending on the editor configuration.
This method returns a promise which resolves with an object, where keys are root names and values are these roots' data. Most editor setups use just one root, which has the default name
main. In this case, the promise will resolve with an object similar to this:{ main: "<p>Sample document data.</p>" }Copy codeIf the adapter integration is used, this method will automatically load necessary
Revision#diffDataif it is missing.Please note, that the data returned by this method uses marked fillers mode. This means that some
characters in the returned data may be wrapped with<span data-cke-filler="true"> </span>. Take this difference into consideration if you plan to compare revision data with the data returned byeditor.getData().See also
getRevisionRootsAttributes.Parameters
revision : Revision
Returns
Promise<Record<string, string>>
getRevisionRootsAttributes( revision ) → Promise<Record<string, Record<string, unknown>>>module:revision-history/revisiontracker~RevisionTracker#getRevisionRootsAttributesReturns roots attributes for given revision.
This method returns a promise which resolves with an object, where keys are root names and values are these roots' attributes. Most editor setups use just one root, which has the default name
main. In this case, the promise will resolve with an object similar to this:{ main: {} }Copy codeSee also
getRevisionDocumentData.Parameters
revision : Revision
Returns
Promise<Record<string, Record<string, unknown>>>
init() → voidmodule:revision-history/revisiontracker~RevisionTracker#initReturns
void
listenTo( emitter, event, callback, [ options ] ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#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
TEvent : extends BaseEventThe type describing the event. See
BaseEvent.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:revision-history/revisiontracker~RevisionTracker#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:revision-history/revisiontracker~RevisionTracker#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
TEvent : extends BaseEventThe type descibing the event. See
BaseEvent.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:revision-history/revisiontracker~RevisionTracker#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
TEvent : extends BaseEventThe type descibing the event. See
BaseEvent.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
saveRevision( revisionData, version ) → Promise<Revision>module:revision-history/revisiontracker~RevisionTracker#saveRevisionCreates and saves a new revision.
// Saves all the unsaved changes as a revision without a name. const myRevision = await revisionTracker.saveRevision(); // Saves all the unsaved changes as a revision named 'My revision'. const myRevision = await revisionTracker.saveRevision( { name: 'My revision' } ); // Saves a revision named 'My revision'. // It will include document data with all the changes up to document version `30`. // The revision will be on "top" of the closest revision with a lower document version. // The revision diff will include all the changes since the previous revision up to document version `30`. const myRevision = await revisionTracker.saveRevision( { name: 'My revision' }, 30 );Copy codeA new revision can be created in the middle of the revision history. In such case, already existing revisions will be appropriately updated.
Using this method, a revision without a name can be created even if the
requireRevisionNameconfiguration option is set totrue.Parameters
revisionData : RevisionDataRevision data to set on the created revision.
Defaults to
{}version : null | numberDocument version on which the revision is saved. If not set, the revision will be saved for the current (most recent) document state.
Defaults to
null
Returns
Promise<Revision>Promise that resolves with the created revision after it is saved locally (the promise does not wait for the adapter update).
set( values ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#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:revision-history/revisiontracker~RevisionTracker#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 : RevisionTracker[ K ]The property's value.
Returns
void
stopDelegating( [ event ], [ emitter ] ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#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:revision-history/revisiontracker~RevisionTracker#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
unbind( unbindProperties ) → voidinheritedmodule:revision-history/revisiontracker~RevisionTracker#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' | 'update' | 'init' | 'isEnabled' | 'licenseKey' | 'editor' | 'isReady' | 'forceDisabled' | 'clearForceDisabled' | 'afterInit' | 'adapter' | 'addRevisionData' | 'getRevisionDocumentData' | 'getRevisionRootsAttributes' | 'currentRevision' | 'repository' | '_revisionDataBuilder' | '_bufferedUpdates' | '_startingVersion' | '_isPendingUpdate' | 'saveRevision' | 'setSource' | 'sendBufferedUpdates' | 'buildRevisionData' | '_bufferUpdate' | 'setRevisionData' | '_createInitialRevision' | '_createCurrentRevision'>Observable properties to be unbound. All the bindings will be released if no properties are provided.
Returns
void
update() → Promise<void>module:revision-history/revisiontracker~RevisionTracker#updateAdds the new document changes to the current revision.
This method should be called before document data and revision data is saved (for example, in the autosave callback).
Returns
Promise<void>Promise that is resolved after the revision is updated locally (the promise does not wait for the adapter update).
Events
change:_isPendingUpdate( eventInfo, name, value, oldValue )module:revision-history/revisiontracker~RevisionTracker#event:change:_isPendingUpdateFired when the
_isPendingUpdateproperty changed value.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
_isPendingUpdate).value : booleanNew value of the
_isPendingUpdateproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
_isPendingUpdateproperty with given key ornull, if property was not set before.
change:isEnabled( eventInfo, name, value, oldValue )module:revision-history/revisiontracker~RevisionTracker#event:change:isEnabledFired when the
isEnabledproperty changed value.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
isEnabled).value : booleanNew value of the
isEnabledproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
isEnabledproperty with given key ornull, if property was not set before.
change:isReady( eventInfo, name, value, oldValue )module:revision-history/revisiontracker~RevisionTracker#event:change:isReadyFired when the
isReadyproperty changed value.Parameters
eventInfo : EventInfoAn object containing information about the fired event.
name : stringName of the changed property (
isReady).value : booleanNew value of the
isReadyproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
isReadyproperty with given key ornull, if property was not set before.
change:{property}( eventInfo, name, value, oldValue )inheritedmodule:revision-history/revisiontracker~RevisionTracker#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.
set:_isPendingUpdate( eventInfo, name, value, oldValue )module:revision-history/revisiontracker~RevisionTracker#event:set:_isPendingUpdateFired when the
_isPendingUpdateproperty 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 (
_isPendingUpdate).value : booleanNew value of the
_isPendingUpdateproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
_isPendingUpdateproperty with given key ornull, if property was not set before.
set:isEnabled( eventInfo, name, value, oldValue )module:revision-history/revisiontracker~RevisionTracker#event:set:isEnabledFired when the
isEnabledproperty 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 (
isEnabled).value : booleanNew value of the
isEnabledproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
isEnabledproperty with given key ornull, if property was not set before.
set:isReady( eventInfo, name, value, oldValue )module:revision-history/revisiontracker~RevisionTracker#event:set:isReadyFired when the
isReadyproperty 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 (
isReady).value : booleanNew value of the
isReadyproperty with given key ornull, if operation should remove property.oldValue : booleanOld value of the
isReadyproperty with given key ornull, if property was not set before.
set:{property}( eventInfo, name, value, oldValue )inheritedmodule:revision-history/revisiontracker~RevisionTracker#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.