Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Route discovery / introspection to workspace #26

Closed
ritch opened this issue Jul 30, 2014 · 4 comments
Closed

Move Route discovery / introspection to workspace #26

ritch opened this issue Jul 30, 2014 · 4 comments

Comments

@ritch
Copy link
Member

ritch commented Jul 30, 2014

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

@raymondfeng
Copy link
Member

I think there are two modes:

  1. Online mode: getting the active api specs from the running instance
  2. Offline mode: getting the api specs from static metadata without running the app

Both are valuable but maybe it's possible to combine them into one place.

@fabien
Copy link

fabien commented Aug 2, 2014

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.

@stale
Copy link

stale bot commented 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.

@stale stale bot closed this as completed Sep 6, 2017
@stale
Copy link

stale bot commented Sep 6, 2017

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.

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

No branches or pull requests

5 participants