Support Boolean fields in conditional hydration - #739
Merged
Conversation
gnawf
reviewed
Jul 22, 2026
gnawf
approved these changes
Jul 22, 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.
Summary
Nadel now accepts Boolean source fields for conditional hydration.
The
equalspredicate acceptstrueandfalse. ThestartsWithandmatchespredicates still require a String or ID field.Nadel reports a validation error when the equals value is not a Boolean.
Tests
Validation tests cover nullable and non-null Boolean fields. They also cover list fields, invalid values, and unsupported predicates.
An integration test confirms that Nadel runs the matching hydration and skips the other hydration.