fix: handle integer flag values serialized as floats#105
Merged
Conversation
JSON doesn't distinguish between int and float numbers, so backends may serialize integer values as 400.0. The SDK now coerces whole-number floats to int when resolving integer flags, and accepts int values when resolving float flags. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
andreas-karlsson
approved these changes
Mar 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
400.0. Updatedprimitive_matchesto accept whole-number floats when expectingint, and acceptintvalues when expectingfloat._selectso resolved values are returned as proper Pythonint.Test plan
test_confidence.pypass (sync, async, edge cases, negative test)test_provider.pypasses (OpenFeature provider layer)🤖 Generated with Claude Code