[bugfix] Custom data model onFetchAvatarPersonaData fix in PeoplePane for stable#4391
Merged
edwardlee-msft merged 5 commits intomainfrom Apr 2, 2024
Merged
Conversation
Contributor
Contributor
Chat bundle size is not changed.
|
Contributor
CallWithChat bundle size is not changed.
|
Contributor
Calling bundle size is not changed.
|
Contributor
@azure/communication-react jest test coverage for beta.
|
Contributor
@azure/communication-react jest test coverage for stable.
|
Contributor
dmceachernmsft
approved these changes
Apr 2, 2024
Contributor
carocao-msft
approved these changes
Apr 2, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Remove unused cc code that was blocking people pane from receiving onFetchAvatarPersonaData in stable
Why
People pane avatars were not being updated despite gallery being updated.
How Tested
MacOS Chrome Calling sample
Process & policy checklist
Is this a breaking change?