"Relation \"[relation]\" is not defined for MyModel model"

[alejandrohenriquez]

Hi:

When I do a query with 3 or more 'joins' I have this error "Relation "[relation]" is not defined for MyModel model":

Example:

var filter: LoopBackFilter = {
            "include": {
                "relation": "company",
                "scope": {
                    "include": {
                        "relation": "installations",
                        "scope": {
                            "include": {
                                "relation": "installation"
                            }
                        }
                    }
                }
            }
        };

this.companyUserApi
    .find(filter)
    .subscribe((x) => {
        console.log('result', x);
    },
    (e) => {
        console.error('error', e.message);
    });

I am not sure if the problem is triggered on the server (Loopback) or in the request (BaseLoopBackApi), but runs well in the loopback explorer view.

The generated url is this:

http://127.0.0.1:3000/api/CompanyUsers?filter[include][relation]=company&filter[include][scope][include][relation]=installations&filter[include][scope][include][scope][include][relation]=installation

Could you help me please ???

Best Regards.

[jonathan-casarrubias]

Hi @k3n3l thanks for reaching me out, hey so... the result query string seems to be correctly formed, not sure what the issue is... I will need to verify in order to know where the issue is.

[jonathan-casarrubias]

@k3n3l I have been verifying today and it looks like that after 3 layers the result is broken, so it looks like the first 2 includes would work but any nested include after that won't work.

I have verified the query string and it is correct, I thinks this may be some issue while LoopBack is parsing really nested queries.

In the explorer works because they encode the json as it is, instead of transforming to query string as I do..

I will try to just encode the json and see if works,

[alejandrohenriquez]

Awesome @jonathan-casarrubias :)
Thank you very much.

[jonathan-casarrubias]

@k3n3l It actually worked but only for those GET methods that uses filter, but not to other GET methods that uses no-filtering params, like custom remoteMethods etc..

So, in order to fix all of the cases I need to handle the request depending if the requests contains a LoopBack Filter or not.

I think I will be pushing the fix today, I just need to finish the unit tests for this.

Cheers!
Jon

[jonathan-casarrubias]

Fixed