Jonathan de Jong

Results 291 issues of Jonathan de Jong

### What Peerings with “sparse” status, an explicit opt in on both sides go allow a connection more low-throughput, high-latency, more unreliable, or with less duty cycles than the current...

Telegram [enabled read receipts](https://telegram.org/blog/chat-themes-interactive-emoji-read-receipts) for small groups, it'd be nice if this could also get reflected in matrix rooms.

### Your use case If i understand soft logout correctly, when an access token becomes invalid (or likewise), users will be kicked back to the login screen, but their user...

S-Tolerable
A-Login
T-Enhancement
A-Soft-Logout
A-Logout
O-Uncommon

When checking https://github.com/matrix-org/matrix-js-sdk/pull/1817, and then looking at https://github.com/matrix-org/matrix-js-sdk/issues/983, i decided to take it upon myself to add a little bit more null-safety to the library. When i added `strictNullChecks` to...

T-Task

This came up while iterating #2137; In `OlmEncryption.encryptMessage`, when iterating over devices per user, the function calls `getStoredDevicesForUser`, which can return `null`. This does not throw an error, as any...

This will remove tons of bugs simply by virtue of function types becoming more correct. Sub-issues; - [ ] `strictNullChecks`: https://github.com/matrix-org/matrix-js-sdk/issues/2112 - [ ] `strictFunctionTypes`: TBD - [ ] https://github.com/matrix-org/matrix-js-sdk/issues/2114...

- https://typescript-eslint.io/rules/no-unsafe-argument - https://typescript-eslint.io/rules/no-unsafe-assignment - https://typescript-eslint.io/rules/no-unsafe-call - https://typescript-eslint.io/rules/no-unsafe-member-access - https://typescript-eslint.io/rules/no-unsafe-return This'll make typescript stricter on `any` usage, disallowing it pretty much anywhere. Most legitimate usages can be replaced with `unknown`....

```ts export interface ISessionInfo { deviceKey?: string; sessionId?: string; session?: string; lastReceivedMessageTs?: number; } interface CryptoStore { getEndToEndSession( deviceKey: string, sessionId: string, txn: unknown, func: (session: ISessionInfo) => void, ):...

https://typescript-eslint.io/rules/no-floating-promises/ https://typescript-eslint.io/rules/no-misused-promises This'd disallow not handling values and errors on promises, and not awaiting promises themselves.

https://typescript-eslint.io/rules/no-throw-literal A lot of code seems to depend on the fact that any thrown error is *at least* some form of `Error`, so this'd help remove the possibility for `undefined`...