[API Request] Start discussion about all the filtering enhancement for the new data #57
Replies: 3 comments 6 replies
-
|
For me, the biggest thing would be to allow sorting and filtering at the same time for the
In other words, allow the It would also be nice to add some additional filtering fields And this could perhaps be a separate discussion, but we should add a new |
Beta Was this translation helpful? Give feedback.
-
|
As an aside, while sorting and filtering are closely linked, I think it's sorting where we need to really make sure to get it right. "Online-first" clients that don't maintain their own synced DB can still do client-side filtering by streaming the paginated APIs through a filter function and discarding the non-matching results, but clients can't implement their own sort orders without requesting the entire catalog ahead of time. |
Beta Was this translation helpful? Give feedback.
-
|
My use cases are basically the same as @dweymouth except with also an option for the total record count of the filter. An additional enhancement (not sure how difficult it would be for servers to implement) is allowing for advanced querying using (nested) filter groups with That way users would be able to query something like: Some examples of this includes:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Type of change
API extension
Proposal description
This is a discussion start to know what the clients needs / wants to enhance filtering in most of the queries to filter on the newly added data.
I personally do all the filtering at the client side and not via the API so clients needs to express their needs.
Backward compatibility impact
No response
Backward compatibility
API details
TBD.
Security impacts
No response
Potential issues
No response
Alternative solutions
No response
Beta Was this translation helpful? Give feedback.
All reactions