-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore | add support for multi filter arguments #151
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #151 +/- ##
============================================
- Coverage 57.57% 56.44% -1.14%
Complexity 264 264
============================================
Files 91 92 +1
Lines 1445 1474 +29
Branches 42 42
============================================
Hits 832 832
- Misses 583 612 +29
Partials 30 30
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
||
@Override | ||
public Single<Filter> convert( | ||
Collection<Collection<AttributeAssociation<FilterArgument>>> filters) { |
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.
Why are we assuming a collection of collection of filters should be an OR-AND
relationship? That's extremely unintuitive. Can we revert this and instead build a real converter here that allows the caller to build relationships - (collection<filters>, logicalOperator) => filter
This reverts commit fd15f6e.
No description provided.