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

rover dev should provide an endpoint to fetch subgraph SDLs #1269

Open
Tracked by #1190
EverlastingBugstopper opened this issue Aug 30, 2022 · 1 comment
Open
Tracked by #1190
Labels
triage issues and PRs that need to be triaged

Comments

@EverlastingBugstopper
Copy link
Contributor

EverlastingBugstopper commented Aug 30, 2022

rover dev spins up a router which embeds sandbox. this sandbox endpoint does not have knowledge of all of the subgraph SDLs, only the API schema provided by the router. this is great for running queries since it's what clients will do, but it's not great for navigability in sandbox itself. the checks page is weird and you can't see all of the different subgraphs in the UI (even though we have UI for displaying multiple subgraph SDLs).

rover dev should spin up a proxy in front of the router, normal requests will pass through to the router, and requests to http://localhost:3000/subgraphs should return a JSON blob of all the subgraphs and their SDL like so:

{
  "subgraphs": {
    "subgraph-a": "subgraph-a SDL",
    "subgraph-b": "subgraph-b SDL",
  } 
}
@abernix
Copy link
Member

abernix commented Aug 31, 2022

would love to be included in this conversation eventually whenever we get to it.

@jonathanrainer jonathanrainer added the triage issues and PRs that need to be triaged label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage issues and PRs that need to be triaged
Projects
None yet
Development

No branches or pull requests

3 participants