From bee751b6afa0c98a408a15e744d32fb65a63e8f5 Mon Sep 17 00:00:00 2001 From: Estelle Comment Date: Thu, 11 Apr 2024 17:02:20 +0200 Subject: [PATCH] Remove old comment --- test/unit-tests/tchap/lib/ExpiredAccountHandler-test.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/unit-tests/tchap/lib/ExpiredAccountHandler-test.ts b/test/unit-tests/tchap/lib/ExpiredAccountHandler-test.ts index f1c763608..9e5cf110c 100644 --- a/test/unit-tests/tchap/lib/ExpiredAccountHandler-test.ts +++ b/test/unit-tests/tchap/lib/ExpiredAccountHandler-test.ts @@ -25,16 +25,16 @@ describe("ExpiredAccountHandler", () => { jest.clearAllMocks(); }); + // TODO : it would be nice to test that our handler is propoerly registered on app load, in src/vector/index.ts + // Gonna require a lot of mocking... it("displays dialog when account is expired", () => { - // handler instance is created when import ExpiredAccountHandler is run. + // handler instance is created when "import ExpiredAccountHandler" is run. ExpiredAccountHandler.register(); // Simulate start of app, for handler to initialise defaultDispatcher.dispatch({ action: "will_start_client" }, true); // Simulate expired error - // cli.on(HttpApiEvent.ORG_MATRIX_EXPIRED_ACCOUNT) - // this.eventEmitter.emit(HttpApiEvent.ORG_MATRIX_EXPIRED_ACCOUNT, err); mockClient.emit(HttpApiEvent.ORG_MATRIX_EXPIRED_ACCOUNT); expect(Modal.createDialog).toHaveBeenCalledWith(