-
-
Notifications
You must be signed in to change notification settings - Fork 648
Allow the embedded client to work without update_state support #4849
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
Conversation
ffdb5b5 to
d805293
Compare
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.
This is surprisingly straight forward.
Thanks Robin!
| sendComplete: jest.fn(), | ||
| }; | ||
|
|
||
| public constructor(clientVersions: ApiVersion[]) { |
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.
tsdoc is welcomed :)
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.
added one
I've revived the changes from #4662 that allow RoomWidgetClient to function even if the client into which it is embedded does not support the
update_stateaction.This seems useful for easing the transition outlined at https://github.com/element-hq/voip-internal/issues/289 with our upcoming Element Call release (for which we want to test some unrelated mobile changes, where mobile currently does not support
update_state), so I propose we add this compatibility layer.