feat: Filter events by DE existence in event [DHIS2-15954] #19778
Conversation
This file contains 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
…events-by-DE-existence
|
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.
Part 2
Continuing the work started in part 1, this PR adds a new
EXoperator, which filters events based on whether a specified data element has a value.The EX operator accepts either
trueorfalse. Iftrue, it filters events where the data value exists; iffalse, it filters events where the data value does not exist.When the
EXoperator used, no other operator is allowed for the sameUID.Previously, the parsing logic for filters was shared between attributes and data elements. To accommodate the new behavior, I had to split it so that it applies only to data elements.