-
Notifications
You must be signed in to change notification settings - Fork 37
feat: expose get_satisfied_experiments and refactor code for resolution #755
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
base: main
Are you sure you want to change the base?
Conversation
Changed Files
|
| ) -> Result<serde_json::Map<String, Value>> { | ||
| self.eval_config(evaluation_context).await | ||
| prefix_filters: Option<Vec<String>>, | ||
| ) -> Result<(serde_json::Map<String, Value>, Vec<String>)> { |
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 we make a type for this?
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.
Aliasing it for now
46e7325 to
5fdfbca
Compare
- Add variants chosen to the Resolution Details so users can validate and debug
5fdfbca to
00fb43c
Compare
mahatoankitkumar
left a comment
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.
TODO for the next PR.
- Making a separate type instead of aliasing.
- And expose these functions in other providers too.
| .await | ||
| } | ||
|
|
||
| pub async fn get_running_experiments_from_provider(&self) -> Result<Experiments> { |
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.
Why call this get_running_experiments_from_provider while using the get_cached_experiments inside? 1-1 naming will be helpful here ?
Problem
Internal juspay systems require more information from the provider to provide adequate debugging information
Solution
Future TODO
Have all s11n providers expose the same interface. This will be done in a future PR