-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat(flagd): Context value hydration #195
base: main
Are you sure you want to change the base?
feat(flagd): Context value hydration #195
Conversation
@@ -114,7 +125,7 @@ def setup_resolver(self) -> AbstractResolver: | |||
): | |||
return InProcessResolver( | |||
self.config, | |||
self.emit_provider_ready, | |||
self.on_provider_ready, |
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.
Should this be emit_provider_ready
? It looks like that's what the event is called elsewhere.
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.
we are wrapping around the initial on_provider_ready event and add another parameter to it, with the contextual attribute. i can not overload the method, else i would have chosen the same name.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #195 +/- ##
==========================================
+ Coverage 94.13% 94.28% +0.15%
==========================================
Files 17 18 +1
Lines 903 928 +25
==========================================
+ Hits 850 875 +25
Misses 53 53 ☔ View full report in Codecov by Sentry. |
cf51d68
to
596c22e
Compare
Signed-off-by: Simon Schrottner <[email protected]>
596c22e
to
a5af90e
Compare
This pr adds context value hydration to the in-process evaluator.
This means, that flagd will provide contextual attributes on connection startup which will be used for inprocess evaluation, like defined in the spec.
https://flagd.dev/reference/specifications/providers/#sync-metadata-properties-in-the-evaluation-context
Follow-up: