Skip to content
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

Conversation

beeme1mr
Copy link
Member

@beeme1mr beeme1mr commented Dec 4, 2023

This PR

  • adds provider-specific evaluation context management

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.

Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
specification/sections/03-evaluation-context.md Outdated Show resolved Hide resolved
specification/sections/03-evaluation-context.md Outdated Show resolved Hide resolved
specification/sections/03-evaluation-context.md Outdated Show resolved Hide resolved
specification/sections/03-evaluation-context.md Outdated Show resolved Hide resolved
specification/sections/03-evaluation-context.md Outdated Show resolved Hide resolved
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
@beeme1mr beeme1mr requested review from a team December 4, 2023 22:06
@beeme1mr beeme1mr marked this pull request as ready for review December 4, 2023 22:06
@beeme1mr beeme1mr requested a review from toddbaert as a code owner December 4, 2023 22:06
@beeme1mr
Copy link
Member Author

beeme1mr commented Dec 4, 2023

I think we should consider introducing the concept of Provider Namespacing. From a feature and implementation perspective, it would essentially be rebranding named clients. Working on this change to the spec (and the corresponding implementation) it was challenging to try and explain how a named provider maps to a specific client.

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".
open-feature/js-sdk#704

Co-authored-by: Kavindu Dodanduwa <Kavindu-Dodan@users.noreply.github.com>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Copy link
Member

@toddbaert toddbaert left a 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)

Copy link
Member

@lukas-reining lukas-reining left a 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>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
@beeme1mr
Copy link
Member Author

beeme1mr commented Dec 5, 2023

Leaving this open for additional feedback until Thursday, December 7.

@beeme1mr beeme1mr merged commit 5ed6c0c into main Dec 8, 2023
4 checks passed
@beeme1mr beeme1mr deleted the 218-manage-context-per-named-provider-when-using-the-static-context-paradigm branch December 8, 2023 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Manage context per named provider when using the static-context paradigm
6 participants