Attached evaluator to provider#50
Conversation
Signed-off-by: Marcin Olko <molko@google.com>
Summary of ChangesHello @m-olko, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request successfully connects the Evaluator to the FlagdProvider, enabling flag evaluation. The changes involve updating the provider to initialize and use an evaluator, and modifying the GetBooleanEvaluation method to delegate to it after checking for provider readiness. The use of std::shared_ptr for the FlagSync object to share it with the evaluator is a reasonable approach. One comment has been retained regarding clarity in a test file.
Signed-off-by: Marcin Olko <molko@google.com>
This PR
Connects Evaluator to Provider
Related Issues
Fixes #40