We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
In one of my project I need to find an object with characteristics store in array in this object. like:
{ name: 'Item1', characteristics: [ { id: 1213, value: 12, otherField: '...', ... }, ], ... }
My search method is based on characteristics Id and value so I wanted to use $elemMatch. But when I used it, an error occured.
'Invalid query parameter $elemMatch'
ctx.app.services.items.find({ query: { characteristics: { $elemMatch: { id: 1213, value: 12, }, } });
What is expected is that the item with a characteristic with id 1213 and value 12 must be retrieve.
Actually the result is an error: 'Invalid query parameter $elemMatch'
I use feathersjs + feathers-mongoose
Module versions (especially the part that's not working): feathers-mongoose: 8.3
NodeJS version: 12.17.0
Operating System: WSL
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
In one of my project I need to find an object with characteristics store in array in this object.
like:
My search method is based on characteristics Id and value so I wanted to use $elemMatch.
But when I used it, an error occured.
'Invalid query parameter $elemMatch'
Steps to reproduce
Expected behavior
What is expected is that the item with a characteristic with id 1213 and value 12 must be retrieve.
Actual behavior
Actually the result is an error: 'Invalid query parameter $elemMatch'
System configuration
I use feathersjs + feathers-mongoose
Module versions (especially the part that's not working):
feathers-mongoose: 8.3
NodeJS version:
12.17.0
Operating System:
WSL
The text was updated successfully, but these errors were encountered: