-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Finish moving query logic #1888
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
Finish moving query logic #1888
Conversation
// Parse.com treats queries on _created_at and _updated_at as if they were queries on createdAt and updatedAt, | ||
// so duplicate that behaviour here. If both are specified, the corrent behaviour to match Parse.com is to | ||
// use the one that appears first in the sort list. | ||
if (sort && sort._created_at) { |
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.
do we need the undefined check for sort
since you've specified the default value?
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.
Probably not. Will change.
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.
Yep it was unnecessary, tests passed without.
@drew-gross updated the pull request. |
DatabaseController.prototype.find no longer depends on the mongo format, I think. Except maybe in count results.