chore: simplify TrackedEntityService.getTrackedEntity(UID, ...) logic DHIS2-18541 #19633
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.
This change is necessary for #19377 and should make changes in behavior easier to see/discuss.
We have two methods for getting a single TE. They were implemented independently with convoluted logic. Let one reuse the other. Separate fetching, ACL, mapping to make the flow easier to follow. Move the TETAV logic in one place. This is the only way we can ensure the behavior is the same across different code paths.
Add an
assertContainsOnly
variant that lets us map both collection before making the actual assertion. This makes the assertion error easier to read.gives you
instead of a giant output with most fields being equal and or irrelevant.