-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wire up the "Forgot recovery key" button for the "Key storage out of sync" toast #29138
Conversation
const recheckSetupRequired = useCallback(() => { | ||
(async () => { | ||
const crypto = matrixClient.getCrypto()!; | ||
const isCrossSigningReady = await crypto.isCrossSigningReady(); | ||
if (isCrossSigningReady) { | ||
setState("main"); | ||
} else { | ||
setState("set_up_encryption"); | ||
} | ||
})(); | ||
}, [matrixClient]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favour to use a custom hook like useSetUpEncryptionRequired
before. It helps the readability of the component imo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like this? I find the custom hook a bit awkward in this scenario since you have to pass a lot of functions around, but I don't mind too much.
src/components/views/settings/tabs/user/EncryptionUserSettingsTab.tsx
Outdated
Show resolved
Hide resolved
if (isCrossSigningReady) { | ||
setState("main"); | ||
} else { | ||
setState("set_up_encryption"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if (isCrossSigningReady) { | |
setState("main"); | |
} else { | |
setState("set_up_encryption"); | |
} | |
if (isCrossSigningReady) setState("main"); | |
else setState("set_up_encryption"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd really rather not if at all possible: I find these line-ifs split over multiple lines very confusing, and I think our code style permits line ifs only if they're one single line.
src/components/views/settings/tabs/user/EncryptionUserSettingsTab.tsx
Outdated
Show resolved
Hide resolved
playwright/e2e/crypto/toasts.spec.ts
Outdated
import { registerAccountMas } from "../oidc"; | ||
import { deleteCachedSecrets } from "./utils"; | ||
|
||
test.use(masHomeserver); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test needs mas?
playwright/e2e/crypto/toasts.spec.ts
Outdated
test.beforeEach(async ({ page, app, mailpitClient }) => { | ||
await page.goto("/#/login"); | ||
await page.getByRole("button", { name: "Continue" }).click(); | ||
await registerAccountMas(page, mailpitClient, "alice", "[email protected]", "Pa$sW0rD!"); | ||
|
||
await expect(page.getByRole("heading", { level: 1, name: "Welcome alice" })).toBeVisible(); | ||
|
||
// We won't be prompted for crypto setup unless we have na e2e room, so make one | ||
await page.getByRole("button", { name: "Add room" }).click(); | ||
await page.getByRole("menuitem", { name: "New room" }).click(); | ||
await page.getByRole("textbox", { name: "Name" }).fill("Test room"); | ||
await page.getByRole("button", { name: "Create room" }).click(); | ||
|
||
// Now set up recovery (otherwise we'll delete the only copy of the secret) | ||
await page.getByLabel("User menu").click(); | ||
await page.getByLabel("All settings").click(); | ||
await page.getByRole("tab", { name: "Encryption" }).click(); | ||
await page.getByRole("button", { name: "Set up recovery" }).click(); | ||
await page.getByRole("button", { name: "Continue" }).click(); | ||
recoveryKey = await page.getByTestId("recoveryKey").textContent(); | ||
await page.getByRole("button", { name: "Continue" }).click(); | ||
await page.getByRole("textbox", { name: "Enter recovery key" }).fill(recoveryKey); | ||
await page.getByRole("button", { name: "Finish set up" }).click(); | ||
|
||
await expect(page.getByRole("button", { name: "Change recovery key" })).toBeVisible(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we use crypto/utils#createBot
to create a second session, bootstrap cross singing and create a recovery key?
crypto/utils#verifySession
can be used to verify the current session too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It took a bit but I think this is working with the bot client now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a crypto point of view, looks OK
Co-authored-by: Florian Duros <[email protected]>
…tofsync_forgotpassword
…sync" toast (#29138) * Wire up the "Forgot recovery key" button for the "Key storage out of sync" toast * Unused import & fix test * Test 'forgot' variant * Fix dependencies * Add more toast tests * Unused import * Test initialState in Encryption Tab * Let's see if github has any more luck running this test than me * Working playwright test with screenshot * year * Convert playwright test to use the bot client * Disambiguate Co-authored-by: Florian Duros <[email protected]> * Add doc & do other part of rename * Split out into custom hook * Fix tests --------- Co-authored-by: Florian Duros <[email protected]> (cherry picked from commit 9657d39)
Fixes #29118
Checklist
public
/exported
symbols have accurate TSDoc documentation.