Add support for integer types in compare function to resolve Force Value attributes issue #33
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.
Features and Changes
This PR addresses the 'Force Value attributes issue' where the compare function only accepted float64 type data, limiting compatibility with integer attributes in GrowthBook. The function has been enhanced to accept int, int32, and int64 types, aligning with GrowthBook's number attribute specifications (which can be float or integer).
Changes
These updates improve flexibility and ensure the compare function fully supports all numeric attributes in GrowthBook.
Testing
Screenshots