-
-
Notifications
You must be signed in to change notification settings - Fork 158
Bug: sorting on multiple fields does not work #745
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
Comments
Also use cases with multiple sorts on the same entity like |
How is that use case different from the problem stated? |
It may not be...Just wanted to point out that if there were no related entities involved, the multiple sort does not work either. From your example, if you specify sort by |
Ah, I understand now. My example could have been clearer. with 'author' I meant a single string attribute containing the author name, not a relationship. I don't think specifying a relationship in sort is possible -- at least, I would not know what sort=author means when author is a relationship, because it does not indicate on which author attribute to sort. |
@bart-degreed thank you for your patience. |
No problem :) |
Uh oh!
There was an error while loading. Please reload this page.
A query like /api/articles?sort=authorName,-pageCount should sort on author, and within that subset sort in pageCount in descending order.
QueryableExtensions contains two methods:
But the second one (building query based upon a parent ordering) is never called.
The text was updated successfully, but these errors were encountered: