-
Notifications
You must be signed in to change notification settings - Fork 40
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
define how context can be managed for named provider using static context paradigm #221
define how context can be managed for named provider using static context paradigm #221
Conversation
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
I think we should consider introducing the concept of Here's the PR that implements the proposed changes. Notice how the JSDocs refer to the scoped provider as a "named client". I think it would be more clear to say "namespaced provider". |
Co-authored-by: Kavindu Dodanduwa <Kavindu-Dodan@users.noreply.github.com> Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
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.
Approved pending #221 (comment)
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.
Looks good to me!
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
…sing-the-static-context-paradigm
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Leaving this open for additional feedback until Thursday, December 7. |
This PR
Related Issues
Fixes #218
Notes
Addresses a limitation in the web SDK where it was impossible to manage context for specific providers. See this issue for more information.