search

open-feature / spec

OpenFeature specification
https://openfeature.dev
Apache License 2.0
588 stars 35 forks source link

define how context can be managed for named provider using static context paradigm #221

Closed beeme1mr closed 6 months ago

beeme1mr commented 7 months ago

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.

beeme1mr commented 7 months ago

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". https://github.com/open-feature/js-sdk/pull/704

beeme1mr commented 7 months ago

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