nikrozman/element-web
1
0
Fork 0
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Conform more of the codebase to strictNullChecks (#10504

Browse Source 
* Conform more of the codebase to `strictNullChecks`

* Iterate
This commit is contained in:
Michael Telatynski
2023-04-04 11:41:46 +01:00
committed by GitHub
parent 6db0c7a1a6
commit bc60a9b594
18 changed files with 60 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/components/views/dialogs/security/CreateCrossSigningDialog.tsx
View File

@@ -32,12 +32,12 @@ import InteractiveAuthDialog from "../InteractiveAuthDialog";
interface IProps {
accountPassword?: string;
tokenLogin?: boolean;
onFinished?: (success?: boolean) => void;
onFinished: (success?: boolean) => void;
}
interface IState {
error: Error | null;
canUploadKeysWithPasswordOnly?: boolean;
canUploadKeysWithPasswordOnly: boolean | null;
accountPassword: string;
}
@@ -73,7 +73,7 @@ export default class CreateCrossSigningDialog extends React.PureComponent<IProps
private async queryKeyUploadAuth(): Promise<void> {
try {
await MatrixClientPeg.get().uploadDeviceSigningKeys(null, {} as CrossSigningKeys);
await MatrixClientPeg.get().uploadDeviceSigningKeys(undefined, {} as CrossSigningKeys);
// We should never get here: the server should always require
// UI auth to upload device signing keys. If we do, we upload
// no keys which would be a no-op.