introduced empty rql filter#2397
Merged
thjaeckle merged 1 commit intoeclipse-ditto:masterfrom Apr 9, 2026
Merged
Conversation
480a524 to
184a81a
Compare
184a81a to
13d56f2
Compare
Member
|
System tests run revealed some errors: |
13d56f2 to
417a778
Compare
Member
|
System tests run: Just contains 1 error which is known to sometimes fail (unrelated to the changes) ✅ |
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.
Resolves: #2377
Summary
Introduces a new RQL filter function
empty(<field>)that returns true when a field is absentor void of content (null, empty array, empty object, empty string), regardless of its JSON type.
This enables use cases like finding all things where e.g.
attributes/tagseither doesn't existor is an empty array — which was previously not expressible in a single RQL filter.