Closed AaronM04 closed 8 years ago
This is with a remote method configured as follows:
user.remoteMethod "<snip>",
http: { verb: "post", path: "/:id/<snip>/:fk" }
accepts:[
{ arg: "id", type: "number", required: true }
{ arg: "fk", type: "number", required: true }
{ arg: "questions", type: "array[object]", required: true }
{ arg: "ctx", type: "object", required: true, http: (ctx) -> ctx }
]
returns: { type: "object", root: true }
Could this have anything to do with the ctx argument (which is recursively defined)?
I think ctx
has circular references. It should be excluded from coercion.
@STRML @bajtos We should exclude req
, res
, and ctx
from coercion.
I agree, as I mentioned before, the patch was merged half-finished. 2.23.0 should not have been released.
I apologise for the troubles. I am going to revert the patch that introduced this problem - see https://github.com/strongloop/strong-remoting/pull/269
Should be fixed in v2.23.1
.
Hi, so I did an npm install without upgrading my loopback version, and it bumped loopback's strong-reporting dependency from v2.22.0 to the next minor version. Now I get an infinite recursion: