fix: normalize booleans on join payloads#1690
Merged
filipecabaco merged 2 commits intomainfrom Feb 3, 2026
Merged
Conversation
filipecabaco
force-pushed
the
fix/infer-boolean-strings-join-payload
branch
from
cc483f7 to
be13b40
Compare
filipecabaco
force-pushed
the
fix/infer-boolean-strings-join-payload
branch
2 times, most recently
from
7387ce0 to
0b8f978
Compare
edgurgel
reviewed
Feb 3, 2026
To ensure better compatibility with existing users we will infer intent from non boolean values by normalizing and downcasing boolean strings e.g. False will be considered false boolean value
filipecabaco
force-pushed
the
fix/infer-boolean-strings-join-payload
branch
from
0b8f978 to
3f17c80
Compare
Member
|
🎉 This PR is included in version 2.74.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
4 participants
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.
What kind of change does this PR introduce?
To ensure better compatibility with existing users we will infer intent from non boolean values by normalizing and down casing boolean strings
e.g.
'False'will be consideredfalseboolean value