Using loopback-connector-remote to call custom methond in another loopback service doesn't create correct URL

[malave]

I'm trying to connect 2 loopback services, let's say A and B, using loopback-connector-remote datasource.

On B I have this custom remote method:

/api/B/myModel/myMethod/{id}

This method works fine if I access the API explorer on B service.

Then on A service I want to access this method so I created the following configuration (which is the same on B too) on the remote model object:

 myModel.remoteMethod(
       'myMethod',
        {
         http: {path: '/myMethod/:id', verb: 'get'},
          accepts: [
           {arg: 'id', type: 'number', required: true}
          ],
          returns: {type: 'object', root: true}
        }
     );

From A I can do any call to B like find, findById, etc. But When I call this custom method I get this error on A:

strong-remoting:rest-adapter Error in GET /myModel/myMethod/1231: Error: id must be a number

And looking at the logs in B I saw that A is calling the service like this:

strong-remoting:rest-adapter Error in GET /myModel/myMethod/:id?id=1231: Error: id must be a number

Why is strong-remoting or loopback-connector-remote not replacing the id correctly when the URL is created? Did I missed something on the configuration?

[richardpringle]

@malave, try this:

{ arg: 'id', type: 'number', required: true, http: { source: 'path' }}

Let me know if that works. If not, could you fork a sandbox for me with the steps to reproduce in the readme? I do understand how to reproduce but a forked sandbox will save me a little more time, which can then be spent fixing the issue. But hopefully it's just the http.source parameter that was missing.

Good luck!

[malave]

@richardpringle Yes that solved the problem. Thanks