Skip to content
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

fix(flagd): handle falsy target values correctly #214

Merged
merged 5 commits into from
Mar 18, 2025

Conversation

AdityaVallabh
Copy link
Contributor

This PR

Prevents erroneous exception when dealing with falsy values.

Related Issues

Fixes #213

Notes

N/A

Follow-up Tasks

N/A

How to test

Added a bunch of UTs.

@AdityaVallabh AdityaVallabh requested a review from a team as a code owner March 16, 2025 06:19
Signed-off-by: AdityaVallabh <aganti@abstract.security>
Copy link

codecov bot commented Mar 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.00%. Comparing base (1b9b5f1) to head (e7ad1f6).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #214      +/-   ##
==========================================
+ Coverage   93.89%   94.00%   +0.10%     
==========================================
  Files          18       18              
  Lines         950      950              
==========================================
+ Hits          892      893       +1     
+ Misses         58       57       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Member

@aepfli aepfli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for your great contribution. This solves your issue as described, but i am not sure, we want to continue in the future with exceptions anyways for handling our flow. Hence i wrote a little comment, and hope some of the Python-masters can help and guide us.

Signed-off-by: AdityaVallabh <aganti@abstract.security>
Signed-off-by: AdityaVallabh <aganti@abstract.security>
Copy link
Member

@beeme1mr beeme1mr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@beeme1mr beeme1mr requested a review from gruebel March 17, 2025 16:41
Copy link
Member

@gruebel gruebel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 🍻 if you need help with the lints let me know.

Signed-off-by: AdityaVallabh <aganti@abstract.security>
@gruebel gruebel merged commit fafd099 into open-feature:main Mar 18, 2025
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] FILE resolver type falls back to default value
4 participants