4 Commits (6392759bec51e6c2502f628fda98f45ea2ba70ed)

Author	SHA1	Message	Date
Andy Balaam	f63160f384	Simplify display of verification requests in timeline (#11931) ... * Simplify display of verification requests in timeline * Comment explaining the purpose of MKeyVerificationRequest	2023-11-30 17:41:47 +00:00
Richard van der Hoff	b9b93264b6	Remove references to `VerificationRequest` (#11050) ... * Update references to `VerificationRequestEvent` * Update references to `Phase` * update references to legacy `PHASE_*` constants * Replace `request.canAccept` with `canAcceptVerificationRequest` * Replace `VerificationRequest` with the interface throughout * Minor strict type fixes * Add a couple of tests	2023-06-14 14:35:32 +00:00
Richard van der Hoff	34439ee652	Simplify references to `VerificationRequest` (#11045) ... * Use new `VerificationRequest.getQRCodeBytes()` * Use new `VerificationRequest.otherDeviceId` * Remove references to `VerificationRequest.channel` * Replace references to `VerificationRequest.{requesting,receiving}UserId` Normally these are guarded by `request.initiatedByMe` so we can trivially replace it with `request.otherUserId` or `client.getUserId()`. In one place we actually need to apply some logic. * increase test coverage * Even more test coverage * Even more test coverage	2023-06-07 14:43:44 +00:00
Richard van der Hoff	2801afe570	Inline `VerificationRequest.{invalid,ready,started,done,cancelled}` (#11013) ... * Inline `VerificationRequest.{invalid,ready,started,done,cancelled}` These methods are all just shortcuts for checks on `phase`, so let's get rid of them * update test * Add some more tests * even more coverage * fix tests	2023-06-06 08:27:53 +00:00