-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
Prevent double mute status changed events #2522
Conversation
Audio & video mute status were set in separate calls but share a mute status changed event, so you'd always get two mute status changed events emitted. We could suppress events where the mute status didn't change, but this would still get two events saying the same thing when they both changed. Instead, merge setAudioMuted & setVideoMuted into a single call that sets either or both. Port of #2502 from group call branch
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.
LGTM otherwise
* @param muted is the feed's video muted? | ||
*/ | ||
public setVideoMuted(muted: boolean): void { | ||
this.videoMuted = muted; | ||
public setAudioVideoMuted(audioMuted: boolean, videoMuted: boolean): void { |
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.
Marked this as a breaking change, any chance you fancy keeping the old ones around for compatibility but just calling the new one under the hood?
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 just internal js-sdk API, so shouldn't need to be a breaking change (although of course it's a public method on an object that the API consumer gets given, so they could call it, but it wouldn't really do anything useful).
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 would argue that there could be a client that is actually using this - we have placeCallWithCallFeeds()
so a client could construct its own CallFeed
s and manipulate them
@dbkr, I think this can be merged now? |
so it can! |
Audio & video mute status were set in separate calls but share a
mute status changed event, so you'd always get two mute status
changed events emitted. We could suppress events where the mute
status didn't change, but this would still get two events saying
the same thing when they both changed. Instead, merge setAudioMuted
& setVideoMuted into a single call that sets either or both.
Port of #2502 from
group call branch
Checklist
This change is marked as an internal change (Task), so will not be included in the changelog.