-
Notifications
You must be signed in to change notification settings - Fork 171
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
GraphiQL set up incorrectly according to docs #179
Comments
@djhi Why was this closed? The new GraphiQL handler is still broken. |
Read too fast... |
You can open PRs by the way :) |
Doing it now! Give me 2 seconds :) |
@djhi I seem to not have the power to make a branch. Can you give me permissions? |
You have to fork the repo, make your change on your fork and you should then have a button to submit a PR :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What you were expecting:
Docs clearly say to register your express server handler at
/graphql
. Then GraphiQL should work once the server starts.What happened instead:
GraphiQL loads
index.html
, but fails to fetch schema or make requests. All requests 404 as they are directed at the wrong handler path.Steps to reproduce:
/graphql
as path like docs say.Related code:
See:
\graphql
or configurable to match a custom pathMore info
GraphiQL is making requests to the wrong express handler due to a misconfiguration. If I register the handler at the base express path
/
, then it works fine.Environment
Node
The text was updated successfully, but these errors were encountered: