-
Notifications
You must be signed in to change notification settings - Fork 70
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
update to support transfer #247
base: main
Are you sure you want to change the base?
update to support transfer #247
Conversation
onClick={async () => this.incomingCall.accept(await this.acceptCallMicrophoneUnmutedVideoOff())}> | ||
onClick={async () => { | ||
this.incomingCall.accept(await this.acceptCallMicrophoneUnmutedVideoOff()); | ||
this.props.onReject(); |
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.
why are we calling onReject here?
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 took this part from another PR that had some initial scaffolding, I'm not sure why. It seems to work as intended. Will ask original author
@@ -67,11 +68,11 @@ export default class CallCard extends React.Component { | |||
canSpotlight: this.capabilities.spotlightParticipant?.isPresent || this.capabilities.spotlightParticipant?.reason === 'FeatureNotSupported', | |||
canMuteOthers: this.capabilities.muteOthers?.isPresent || this.capabilities.muteOthers?.reason === 'FeatureNotSupported', | |||
canReact: this.capabilities.useReactions?.isPresent || this.capabilities.useReactions?.reason === 'FeatureNotSupported', | |||
videoOn: this.call.isLocalVideoStarted, |
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.
Nit: why remove the usage of isLocalVideoStarted
? I'd suggest to keep this in as this is a sample and isLocalVideoStarted
is a GA API on the SDK.
screenSharingOn: this.call.isScreenSharingOn, | ||
micMuted: this.call.isMuted, | ||
videoOn: !!props.call.localVideoStreams[0], | ||
screenSharingOn: props.callIsScreenShareOn, |
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.
props.call.isScreenSharingOn
?
return; | ||
} | ||
try { | ||
var id = {communicationUserId: this.destinationUserId.value} |
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.
var id = {communicationUserId: this.destinationUserId.value} | |
const id = {communicationUserId: this.destinationUserId.value} |
onClick={async () => this.incomingCall.accept(await this.acceptCallMicrophoneUnmutedVideoOff())}> | ||
onClick={async () => { | ||
this.incomingCall.accept(await this.acceptCallMicrophoneUnmutedVideoOff()); | ||
this.props.onReject(); |
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 think the reject here is a hack, we shall fix it properly by cleaning up old call/state and adding the new one
onClick={async () => this.incomingCall.accept(await this.acceptCallMicrophoneUnmutedVideoOn())}> | ||
onClick={async () => { | ||
this.incomingCall.accept(await this.acceptCallMicrophoneUnmutedVideoOn()); | ||
this.props.onReject(); |
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.
same here
Purpose
Does this introduce a breaking change?
Pull Request Type
What kind of change does this Pull Request introduce?
How to Test
What to Check
Verify that the following are valid
I manually tested stuff within calls (video, video effects, call holding, resuming, spotlight, raise hand within transfer flows (before and after transfer). Probably did not test every scenario
Other Information