Do not pass the Capabilities for the global endpoint demo #2735
Conversation
This file contains 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
xuesichao
approved these changes
Aug 19, 2023
simmkyu
added a commit
that referenced
this pull request
Aug 19, 2023
…and "Do not pass the Capabilities for the global endpoint demo (#2735)"
xuesichao
pushed a commit
that referenced
this pull request
Aug 19, 2023
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.
Issue #:
N/A
Description of changes:
Testing:
N/A. Only a demo change
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
In the demo application using the legacy Chime SDK global endpoint, the attendee capability feature should be unaffected. I've preserved the attendee capability UI for the global endpoint demo because we plan to deprecate the global endpoint soon.
Checklist:
Have you successfully run
npm run build:releaselocally?N/A
Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
No
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.