Conversation
Levdbas
marked this pull request as draft
September 11, 2026 20:08
Contributor
Author
|
Waiting for #202 to be merged in |
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.
Add Support for Operator-Only Conditions
This pull request recreates the functionality proposed in the closed PR #187.
Thank you to the original author, @nlemoine.
Changes
valuefor single-operator conditions such as!=empty.and()andor()calls.valuekey entirely when no value is supplied, matching ACF's expected configuration format.InvalidArgumentExceptionwhen one is omitted.Validation
ConditionalBuilderTestpasses, including operator-only constructor and fluent-chain coverage.LocationBuilderTestpasses, including required-value coverage.ParentDelegationBuilderTest:MockBuilder::setMethods()has been removed.