-
Notifications
You must be signed in to change notification settings - Fork 1
fix: Report a type mismatch for non-numeric flag values #29
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
Open
kinyoklion
wants to merge
1
commit into
main
Choose a base branch
from
devin/1788211220-php-numeric-type-check
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
It's been a bit since I've looked at this part of the algorithm, but do we typically do this truncation?
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.
Yes — truncation is what the other server providers do, which is why I matched it rather than treating a non-integral float as a type mismatch:
_LaunchDarklyProvider__validate_and_cast_value:return int(value) # Float decimals are truncated to intforFlagType.INTEGER.provider.rbinteger resolution:evaluation_detail.value.to_i.resolveNumberEvaluation, so the question does not arise there.Both accept an
intor afloatand reject bools and numeric strings, which is exactly the shape of the check here.Worth being explicit that truncation is not what this PR is really about, though: before it,
is_numericlet a non-integral float through uncast, soresolveIntegerValuereturned5.5and the OpenFeature client raised aTypeErrorthat surfaced asGENERALrather than anything meaningful. So the choice is between truncating like Python and Ruby, or returningTYPE_MISMATCHwith the default value. I went with the former for cross-SDK consistency, but if you would rather a5.5integer flag be a hardTYPE_MISMATCHhere I am happy to switch it — it is a one-line change plus the test, and it would be a deliberate divergence from Python and Ruby.