-
Notifications
You must be signed in to change notification settings - Fork 20
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: Feature Provider Enhancement - #321 #324
feat: Feature Provider Enhancement - #321 #324
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #324 +/- ##
==========================================
+ Coverage 85.91% 86.66% +0.75%
==========================================
Files 34 34
Lines 1377 1387 +10
Branches 148 147 -1
==========================================
+ Hits 1183 1202 +19
+ Misses 162 153 -9
Partials 32 32 ☔ View full report in Codecov by Sentry. |
@toddbaert @askpt @beeme1mr Hi guys, I hope you are doing well! 🖐 |
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.
LGTM! It seems that some of the DI extension classes are missing coverage. I wonder if it is worth excluding them from code coverage for the build to pass.
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.
Hey @arttonoyan, sorry for the delay. Last week was a holiday in the US.
The change looks good to me. Should the examples in the readme also be updated?
Oh, no problem! I forgot about that. 😊 Yes, of course, I’ll update the documentation as well. I just wanted to get your feedback first, and I’ll make sure to update it before merging. |
@ghelyar does this solve the issues you mentioned? |
yes |
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.
This looks good to me and addresses the outside feedback.
My only blocker is updated documentation. Once you have that I can squash down the commits to one for you to sign off on if you want, @arttonoyan .
Thanks, @toddbaert ! I’ve updated the document, and I think this version is much more flexible - I’m really happy with how it’s shaping up. It’s great to see external feedback coming in; it’s been super helpful. |
…erience Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
…e#323) When provider resolutions with error code set other than `None` are returned, the provider acts as if an error was thrown. Signed-off-by: christian.lutnik <christian.lutnik@dynatrace.com> Signed-off-by: Artyom Tonoyan <arttonoyan@gmail.com>
acd5c50
to
e383697
Compare
Hey @toddbaert, it looks like this PR is ready! Could you please take a look when you have a moment? |
Hey @toddbaert, just a friendly reminder to take a look when you have a moment. 😊 |
This update focuses on enhancing the feature provider integration and testing framework, incorporating improvements to flexibility, usability, and testing capabilities.
This update addresses GitHub Issue #321 in the OpenFeature .NET SDK repository.
Key Enhancements
Dependency Injection (DI) Enhancements:
AddProvider
extension method to simplify and adapt feature provider integration during service setup.Simplified Codebase:
FeatureProviderFactory
logic, eliminating unnecessary complexity and improving usability.Improved InMemoryProvider:
InMemoryProvider
, enabling smoother and more intuitive usage.Testing Improvements:
Example: Service Registration and Usage
Service Registration
FlagConfigurationService Implementation