-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Add E2EE for embedded mode of Element Call #3667
Conversation
and also move some code to a more sensible place in the file
Then we can initialise from the state once it's completed.
& add log line
private onTimeline = (event: MatrixEvent): void => { | ||
if (event.getType() !== EventType.CallEncryptionKeysPrefix) return; | ||
|
||
const room = this.client.getRoom(event.getRoomId()); | ||
if (!room) { | ||
logger.error(`Got room state event for unknown room ${event.getRoomId()}!`); | ||
return; | ||
} | ||
|
||
this.getRoomSession(room).onCallEncryption(event); | ||
}; |
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.
Non-blocking, but I'm not convinced that this callback belongs in the session manager class. I think it makes most sense if the session manager is only responsible for creating, ending, and storing sessions, so this feels better suited for the session class itself.
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.
Yeah, I think I would agree: I guess it was sticking to the pattern of all the events going into the manager and being dispatched from there.
Based on #3663
For element-hq/element-call#1350
Here's what your changelog entry will look like:
✨ Features