Query nested properties

[juncoding]

I'm not sure it's a bug or a new feature, but the behavior is not same as loopback find/findOne.

=== Sample Code ===

var applyFilter = require('loopback-filters');
var data = [
    {foo: [{name: 'bar'}, {name: 'bar2'}]},
    {bat: [{name: 'baz'}]},
    {foo: [{name: 'bar'}]}
];
var filter = {where: {"foo.name": 'bar'}};
var filtered = applyFilter(data, filter);
console.log(filtered);

=== Expected result ===

[ {foo: [{name: 'bar'}, {name: 'bar2'}] }, { foo: [{name: 'bar'} ]

=== Actual result ===

[]

but I use loopback model.find/findOne, I can get expected result.

Please help. Thanks.

[bajtos]

I think you are looking for support for querying nested properties, which was added to loopback-datasource-juggler (and thus find/findOne methods) via loopbackio/loopback-datasource-juggler#1239 and possibly other pull requests related to strongloop/loopback#517.

Ideally, loopback-datasource-juggler's memory connector would be using loopback-filters under the hood and there was only a single place where to add support for new filtering features. Unfortunately we haven't had bandwidth to do that change, and as a result loopback-filters is always behind loopback capabilities. Any volunteers to contribute this change?

As a short-term workaround, we can always port loopbackio/loopback-datasource-juggler#1239 (and other related pull requests) from juggler to this module. We don't have bandwidth for this task ourselves, but we are happy to help you if you decide to contribute this feature.

[bajtos]

I created a new issue in juggler to keep track of the work of using loopback-filters under the hood: loopbackio/loopback-datasource-juggler#1529

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.