You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within other SDKs, we're able to set a context on a client level. Although there is a field within the client, there is no setter for the evaluation context.
We should be able to set a client wide evaluation context, and it should behave as described.
I'd like to tackle this — plan to add set_evaluation_context() on the client and merge it with the provider-level context per the spec. PR coming shortly.
Activity
feat: add set_evaluation_context method to OpenFeatureClient
vikasrao23 commentedon Feb 21, 2026
Hi! 👋
I've implemented this feature in PR #565.
What was added
set_evaluation_context(context)method to theOpenFeatureClientclassImplementation details
The client context is now settable and is properly merged during flag evaluation with the correct precedence:
API context → Transaction context → Client context → Invocation context
This matches the behavior described in the OpenFeature spec's context merging feature.
Example usage:
Let me know if any adjustments are needed!
feat: add set_evaluation_context and get_evaluation_context to OpenFe…
feat: add set_evaluation_context and get_evaluation_context to OpenFe…
balgaly commentedon Apr 14, 2026
I'd like to tackle this — plan to add set_evaluation_context() on the client and merge it with the provider-level context per the spec. PR coming shortly.
feat(client): add get/set_evaluation_context methods
danjuv commentedon Apr 15, 2026
Perhaps this issue needs rescoping. @gruebel mentioned the solution is the missing E2E tests but that's not immediately clear from the description.
test(e2e): add Behave step definitions for context merging
test(e2e): add Behave step definitions for context merging
test(e2e): add Behave step definitions for context merging (#593)