Base class for verification methods.
Once a verifier object is created, the verification can be started by calling the verify() method, which will return a promise that will resolve when the verification is completed, or reject if it could not complete.
Subclasses must have a NAME class property.
the verification channel to send verification messages over. TODO: Channel types
base matrix api interface
the user ID that is being verified
the device ID that is being verified
the m.key.verification.start event that initiated this verification, if any
the key verification request object related to this verification, if any
Private
_doneReadonly
basebase matrix api interface
Private
cancelledReadonly
channelthe verification channel to send verification messages over. TODO: Channel types
Readonly
devicethe device ID that is being verified
Protected
Optional
doProtected
Optional
expectedPrivate
promisePrivate
Optional
rejectPrivate
Optional
rejectReadonly
requestthe key verification request object related to this verification, if any
Private
Optional
resolvePrivate
Optional
resolvethe m.key.verification.start event that initiated this verification, if any
Private
Optional
startedPrivate
transactionReadonly
userthe user ID that is being verified
Rest
...args: Parameters<VerificationEventHandlerMap[T]>Rest
...args: Parameters<Arguments[T]>Private
endOptional
event: EventEmitterEvents | Cancel | EventsPrivate
resetProtected
sendProtected
verifyProtected
waitGenerated using TypeDoc
Typed Event Emitter class which can act as a Base Model for all our model and communication events. This makes it much easier for us to distinguish between events, as we now need to properly type this, so that our events are not stringly-based and prone to silly typos.