-
-
Notifications
You must be signed in to change notification settings - Fork 750
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
feathers-rest, how to query using $in? #497
Comments
it is actualy works when the array of _id is not empy |
It looks like this is how Node's querystring module behaves (see nodejs/node-v0.x-archive#7971 for a discussion). Since it is using URL strings, there is always limitations (e.g. conversion and things like empty values etc.) imposed when using the REST clients (this is not an issue when using websockets). Adding |
* Updating changelog * fixing the authentication config key that is referenced. Closes #497 * Work with 'authentication' or 'auth' config key * Fix reference to app -> this.app
* Updating changelog * fixing the authentication config key that is referenced. Closes #497 * Work with 'authentication' or 'auth' config key * Fix reference to app -> this.app
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs. |
Steps to reproduce
call api using feathers rest client
app.service('platforms').find({ query: { _id: { $in: [1, 3, 6] }, $sort: { fans: -1 } } })
Expected behavior
return platforms collection filtered by _id $in [1,3,6]
Actual behavior
return all platforms collection because the _id filter $in not generated to the query string
System configuration
NodeJS version:
6.9.1
Operating System:
Win 10
Browser Version:
Chrome
The text was updated successfully, but these errors were encountered: