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
The ability to introspect routes, swagger resources, and other related meta data, should be made available from the workspace API. The explorer should use the workspace API to get the metadata it needs instead of interacting with the app directly.
There's another thing on my mind. Whereas strongloop-remoting/ext/swagger was agnostic to the remotes provider, it now depends on a LB app specifically. In other words, I used to be able to explore any kind of strong-remoting api, but this is no longer possible as it now only handles LB Models.
It'd be great if loopback-explorer could be generalized to accept remotes from other places.
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.
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.
The ability to introspect routes, swagger resources, and other related meta data, should be made available from the workspace API. The explorer should use the workspace API to get the metadata it needs instead of interacting with the
app
directly./cc @raymondfeng
The text was updated successfully, but these errors were encountered: