-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
GET on collection with 'sort' parameter fails #1786
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
|
Tried both. No change in behavior. @drew-gross |
I checked with api.parse.com, and api.parse.com won't crash if you pass a "sort" parameter, but it also won't actually sort the data. The parameter you need to use is "order". |
Thanks Drew. That did the trick. I guess it was a bug that we brought over from Parse.com. Once I changed it to order I then get the exception that _createdAt is not a valid key. Once I changed it to createdAt everything works. Thank you. Please close. |
Check out #1271 for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
Many members of the community use Stack Overflow and Server Fault to ask questions. Read through the existing questions or ask your own!
For database migration help, please file a bug report at https://parse.com/help#report
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
Steps to reproduce
When the following code is called
The response is
{"code":102,"error":"Invalid paramater for query: sort"}
Of course if we remove the sort then everything works fine.
The text was updated successfully, but these errors were encountered: