You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GET on collection with 'sort' parameter fails #1786
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!
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.
Activity
drew-gross commentedon May 13, 2016
_createdAtis not a valid key. Try_created_atorcreatedAt.araskin commentedon May 13, 2016
Tried both. No change in behavior. @drew-gross
drew-gross commentedon May 13, 2016
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".
araskin commentedon May 13, 2016
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.