-
Notifications
You must be signed in to change notification settings - Fork 734
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
Please check if the endpoint 'undefined' is a valid GraphQL Endpoint. #287
Comments
@dalejefferson I think the problem is, that you're providing It's deployed here: https://1rp2h4rth8.execute-api.us-east-1.amazonaws.com/dev/playground Does that solve your issue? The issue for the |
I'm experiencing the same problem. While I haven't yet found a fix, I have found a workaround that hopefully helps diagnose the root problem. For me, using the default
But if I change the http path to |
I've just upgraded to |
This issue pertains to:
What OS and OS version are you experiencing the issue(s) on?
Mac OS, Chrome 63, AWS Lambda Node 6.10
What version of graphql-playground(-electron/-middleware) are you experience the issue(s) on?
1.3.1
What is the expected behavior?
Successfully load the playground
What is the actual behavior?
I see an error message
Strangly queries work so it's just the schema fetching that is broken.
What steps may we take to reproduce the behavior?
Upgrade to graphql-playground-middleware-lambda 1.3.1
The text was updated successfully, but these errors were encountered: