fix: don't init if provider doesn't have an init method #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
initif any of the sub-providers do not have an init methodRelated Issues
Notes
This was blowing up for us because one of our providers does not have an
initmethod. Sinceinitis common but not required per OpenFeature spec for providers, a simpleresponds_to?check makes this safe for all providers.Follow-up Tasks
How to test
Create a MetaProvider using a provider that does not have an
initmethod, such as this one, along with a provider that does have aninitfunction. Calliniton the MetaProvider. Assert thatinitwas not called on the provider without aninitmethod, and that it was called on the provider with aninitmethod.