multi options field - account for querying by ':empty:', ':notempty:' values #17763
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.
Description
When querying the multi-options field (checkboxes or multi-select), account for querying by
':empty:'and':notempty:'values.When column type is JSON, the empty value can be stored as null, empty string, or empty array (`'[]``).
Steps to reproduce:
Filter the element index table by each field (one at a time) and test that “is empty” and “is not empty” work as expected.
Set up a template that queries by multiple values where one of them is
':empty:'or':notempty:'. For example:The result (with this PR):
The result without this PR:
Related issues
n/a; reported by @olivierbon