Bug: boolean with true as default are always true#44
Merged
cpiemontese merged 3 commits intomasterfrom Mar 19, 2026
Merged
Conversation
pau-sala
changed the title
cpiemontese
previously approved these changes
Mar 19, 2026
Contributor
cpiemontese
left a comment
cpiemontese
left a comment
There was a problem hiding this comment.
Wow that's a subtle bug, thanks!
If you can update the CHANGELOG and run a suite-py bump, I will release the patch as soon as this is merged
cpiemontese
approved these changes
Mar 19, 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
2 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.
Ciao!
When writing an integration test using the
avrogengenerated code I've found that a schema with a boolean field with a default set to true will always be true no matter the value, due to this linelib/avrogen/avro/types/record/field.ex:84I've added a test, which fails with the code as is, and a possible fix.
TX!