-
Notifications
You must be signed in to change notification settings - Fork 30
fix!: raise error if the flag wasn't found using the in-memory provider #228
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
Conversation
Signed-off-by: Michael Beemer <[email protected]>
Signed-off-by: Michael Beemer <[email protected]>
|
@beeme1mr writes Python now 😎 |
toddbaert
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.
Makes sense to me conceptually.
federicobond
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.
LGTM
|
Looks like some of the gherkin tests are failing due to the InMemoryFlag change, could you update those so it's ready to merge? |
|
@federicobond I'll try 😟 |
Signed-off-by: Michael Beemer <[email protected]>
Signed-off-by: Michael Beemer <[email protected]>
|
It was easier than I thought... perhaps I am a Python developer now 😄 |
Codecov Report
@@ Coverage Diff @@
## main #228 +/- ##
==========================================
+ Coverage 93.63% 93.84% +0.21%
==========================================
Files 16 16
Lines 440 439 -1
==========================================
Hits 412 412
+ Misses 28 27 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
…1.5 (open-feature#228) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This PR
Notes
I marked this as a breaking fix because it changes the method signature of the in-memory provider. Since we're sub-1.0, this will be treated as a minor version change, but highlight the change more predominately in the change log.
I originally intended to only remove the duplicate keys in this PR. If you would prefer that I split these into two separate PRs, please let me know.