nestRemoting does not appear

[lughino]

I added a layer to the rest api but this does not appear in the component explorer.

// member.json
"relations": {
    "corporates": {
      "type": "hasMany",
      "model": "Corporate",
      "foreignKey": "",
      "options": {
        "validate": true,
        "forceId": false
      }
    },
   ...
}

// corporate.json
"relations": {
    "contests": {
      "type": "hasMany",
      "model": "Contest",
      "foreignKey": "",
      "options": {
        "validate": true,
        "forceId": false
      }
    },
    "member": {
      "type": "belongsTo",
      "model": "Member",
      "foreignKey": "",
      "options": {
        "validate": true,
        "forceId": false
      }
    }
  },

// in boot script
Member.nestRemoting('corporates');

Now I can make calls, eg with postman, like this:

/api/Members/<memberid>/corporates/<corporateid>/contests

But in the component explorer these routes are not displayed.
It's a bug? If not it would be very nice as a new feature!

[jtan4gov]

Any comments on this? We have not seen the routes exposed in the explorer as well. Thanks!

[tjosbon]

Same here, the nested relationships are not showing in explorer.

[jankcat]

Anyone have a workaround, maybe a way to display all active routes in a console.log?

[lughino]

It seems that loopback is really very slow to fix problems.
I am very sorry to say because the starting point is really good, but in a world where the developments are very fast, loopback is left far behind!
Many PR to assess and make the merge, adding features slim to none, nonexistent bug fixes ..
Since it was acquired by ibm it seems that is no longer of interest to them to evolve and improve this framework.

[jtan4gov]

That's sad.

On Nov 1, 2016 6:58 PM, "Luca Pau" notifications@github.com wrote:

It seems that loopback is really very slow to fix problems.
I am very sorry to say because the starting point is really good, but in a
world where the developments are very fast, loopback is left far behind!
Many PR to assess and make the merge, adding features slim to none,
nonexistent bug fixes ..
Since it was acquired by ibm it seems that is no longer of interest to
them to evolve and improve this framework.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#167 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIyv24c-esLwKdzRqRRE6tXrOb7Sfjtcks5q5xtegaJpZM4Ir0V2
.

[sebastianhaas]

@lughino it's sad but I feel exactly the same way. I guess I have >10 discussions open with issues all around the framework, provided multiple showcase apps, even provided tests, tried to help on documentation but I don't think anybody is really taking care of this project anymore. By the end of 2016 I'd recommend anybody to move away.

[jankcat]

@sebastianhaas yup. Already moved to Parse. It has the functionality I need but most importantly it has an active community and is maintained.

[superkhau]

It seems that loopback is really very slow to fix problems.

@sebastianhaas @lughino @jankcat We have many active developers on the project, but unfortunately not every issue gets responded to promptly (there are many priorities to juggle -- there has been discussion in opening up more repos for the community to take over (and perhaps improve on the response times). That said, do you have any suggests on how to improve your experience?

[flvndvd]

See #208