-
Notifications
You must be signed in to change notification settings - Fork 8
fix(explore): skip child filters for default filter #176
base: main
Are you sure you want to change the base?
Conversation
Test Results361 tests ±0 361 ✔️ ±0 14s ⏱️ +4s Results for commit 0aa5dd5. ± Comparison against base commit 525fc0d. This pull request removes 28 and adds 13 tests. Note that renamed tests count towards both.
|
Codecov Report
@@ Coverage Diff @@
## main #176 +/- ##
============================================
- Coverage 81.43% 81.39% -0.05%
Complexity 1323 1323
============================================
Files 125 125
Lines 5951 5954 +3
Branches 490 491 +1
============================================
Hits 4846 4846
- Misses 861 864 +3
Partials 244 244
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@@ -93,12 +93,18 @@ private void addSelections( | |||
|
|||
private Filter.Builder buildFilter( | |||
ExploreRequest exploreRequest, List<String> entityIdAttributeIds, Set<String> entityIds) { | |||
if (org.hypertrace.gateway.service.v1.common.Filter.getDefaultInstance() | |||
.equals(exploreRequest.getFilter())) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we rely on presence check? or is there an upstream bug? Either way, not sure I'm following why entity IDs are ignored if there's no filter? Shouldn't we just not be and'ing and using only the in filter?
No description provided.