feat(calling): export getCallingBackend#5010
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 57241f2459
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| SORT, | ||
| SORT_BY, | ||
| } from './common/types'; | ||
| export {resolveCallingBackend} from './common/Utils'; |
There was a problem hiding this comment.
Export the documented getCallingBackend symbol
When consumers follow the new public API advertised by this change and import getCallingBackend from @webex/calling, the package still has no such named export; this entry point only exports resolveCallingBackend, while the deprecated wrapper's JSDoc also tells users to use getCallingBackend(device). Add or alias the exported function under the documented getCallingBackend name so the new API is actually available.
Useful? React with 👍 / 👎.
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
COMPLETES hidden
This pull request addresses
< DESCRIBE THE CONTEXT OF THE ISSUE >
by making the following changes
< DESCRIBE YOUR CHANGES >
Change Type
The following scenarios were tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
The GAI Coding Policy And Copyright Annotation Best Practices
I certified that
Make sure to have followed the contributing guidelines before submitting.