When an SDK follows the static-context paradigm, context can only be managed from global API object. This is to convey to application authors that changing context may lead to an expensive async operation.
Currently, there's a global evaluation context that's shared across all providers. This can lead to challenges like:
Updating context fires the onContextChange handler for all registered providers.
Unable to manage context for a specific provider.
Context that's valid for one provider may be invalid in another.
Requirements
Define the requirements for managing context per named provider when using the static-context paradigm
toddbaert
commented
7 months ago
Overview
When an SDK follows the static-context paradigm, context can only be managed from global API object. This is to convey to application authors that changing context may lead to an expensive async operation.
Currently, there's a global evaluation context that's shared across all providers. This can lead to challenges like:
onContextChangehandler for all registered providers.Requirements
References