Skip to content

nestRemoting does not appear #167

Closed
Closed

Description

@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!

Activity

  1. jtan4gov commented on Jul 14, 2016

    @jtan4gov

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

  2. tjosbon commented on Aug 12, 2016

    @tjosbon

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

  3. jankcat commented on Nov 1, 2016

    @jankcat

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

  4. lughino commented on Nov 1, 2016

    @lughino
    Author

    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.

  5. jtan4gov commented on Nov 1, 2016

    @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
    .

  6. sebastianhaas commented on Dec 27, 2016

    @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.

  7. jankcat commented on Dec 27, 2016

    @jankcat

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

  8. superkhau commented on Dec 29, 2016

    @superkhau
    Contributor

    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?

  9. flvndvd commented on Mar 29, 2017

    @flvndvd

    See #208

  10. stale commented on Aug 23, 2017

    @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.

  11. sebastianhaas commented on Aug 24, 2017

    @sebastianhaas

    Nest remoting still doesnt work as I would expect it.

  12. sebastianfelipe commented on Sep 14, 2017

    @sebastianfelipe

    Nest remoting doesn't work. It defined the endpoints, but they don't appear on the explorer

  13. raymondfeng commented on Sep 15, 2017

    @raymondfeng
    Member

    I'm seeing the same issue.

  14. raymondfeng commented on Sep 15, 2017

    @raymondfeng
    Member

    I created a fix at #222

  15. raymondfeng commented on Sep 15, 2017

    @raymondfeng
    Member

    Fixed by loopback-component-explorer@5.1.0 or loopback-component-explorer@4.3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions