Add Provider Repository

[NeaguGeorgiana23]

This PR

Adds the Provider Repository and unit-tests for it.

Related Issues

Fixes #31

[gemini-code-assist]

Summary of Changes

Hello @NeaguGeorgiana23, I'm Gemini Code Assist¹! 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 introduces the ProviderRepository component, a core addition to the OpenFeature SDK. Its primary purpose is to centralize and streamline the management of feature providers, allowing for dynamic registration, retrieval, and lifecycle control of both default and domain-specific providers. This enhancement significantly improves the flexibility and robustness of how feature flags are integrated and managed within applications.

Highlights

• New Provider Repository: Introduced a new ProviderRepository class responsible for managing FeatureProvider instances, including a default provider and domain-specific providers.
• Provider Lifecycle Management: The repository handles the initialization and shutdown of feature providers, supporting both synchronous and asynchronous initialization based on configuration.
• Status Management: It integrates with FeatureProviderStatusManager to track the status of each provider (e.g., ready, error, not ready) and ensures proper shutdown of old providers when new ones are set.
• Comprehensive Unit Tests: Extensive unit tests have been added to validate the functionality of the ProviderRepository, covering various scenarios like default initialization, named providers, null provider handling, and shutdown behavior.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a ProviderRepository for managing feature providers, along with corresponding unit tests. The implementation is comprehensive, but there are a few critical issues to address. A potential null pointer dereference could crash the application, and the use of detached threads for asynchronous initialization can lead to use-after-free vulnerabilities and data races. I've also included a suggestion to improve future performance and maintainability by changing how EvaluationContext is passed. The unit tests are well-written and cover many scenarios, but they don't expose the race conditions or lifetime issues.

[oxddr]

As usual, please wait for @alichka06 approval.