-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
3
-
S
Context:
See comment in PR description: https://github.com/camunda/camunda-optimize/pull/3732#issue-695066628
Now that we have quite a few Flownode viewLevel filters that need instance matching, we should adjust the instance and flownode filter methods in ModelElementFilterQueryUtil to ideally have a very similar structure so it's easier to read. Also, adjust `add..Filter` methods to not "double nest" the filters (see explanation in PR) if possible (though we should make sure to double check if this kind of nesting has a reason).
AT:
- ModelElementFilterQueryUtil is easier to read, especially addInstanceFilterForRelevantViewLevelFilters