You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Reacted by sebastianhaas, Flavien David and JaFF92
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.
@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.
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?
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.
Activity
jtan4gov commentedon Jul 14, 2016
Any comments on this? We have not seen the routes exposed in the explorer as well. Thanks!
tjosbon commentedon Aug 12, 2016
Same here, the nested relationships are not showing in explorer.
jankcat commentedon Nov 1, 2016
Anyone have a workaround, maybe a way to display all active routes in a console.log?
lughino commentedon Nov 1, 2016
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 commentedon Nov 1, 2016
That's sad.
On Nov 1, 2016 6:58 PM, "Luca Pau" notifications@github.com wrote:
sebastianhaas commentedon Dec 27, 2016
@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 commentedon Dec 27, 2016
@sebastianhaas yup. Already moved to Parse. It has the functionality I need but most importantly it has an active community and is maintained.
superkhau commentedon Dec 29, 2016
@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 commentedon Mar 29, 2017
See #208
stale commentedon Aug 23, 2017
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.
sebastianhaas commentedon Aug 24, 2017
Nest remoting still doesnt work as I would expect it.
sebastianfelipe commentedon Sep 14, 2017
Nest remoting doesn't work. It defined the endpoints, but they don't appear on the explorer
raymondfeng commentedon Sep 15, 2017
I'm seeing the same issue.
raymondfeng commentedon Sep 15, 2017
I created a fix at #222
raymondfeng commentedon Sep 15, 2017
Fixed by loopback-component-explorer@5.1.0 or loopback-component-explorer@4.3.0.