-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] Can't retrieve schema for GraphQL #1272
Comments
👋 Thanks for opening your first issue! If you're reporting a 🐞 bug, please make sure To help make this a smooth process, please be sure you have first read the |
Would you be able to provide a public GraphQL endpoint to test this with? I have a feeling that the |
@gschier sorry, I'm unable to provide the public endpoint 😞 |
@gschier Any updates on this? |
There isn't much I can do if I can't reproduce it. I just updated the GraphQL dependencies though so maybe that will fix it 😄 |
@gschier A similar thing happens to me on Insomnia 6.3.2; maybe this is a separate issue. When I modify my GQL API, the API URL stays the same so there is no auto-refresh. I have to point-and-click to manually refetch the schema for warnings to disappear. Refetching the schema somehow automatically, like in previous versions, would be nice in development, where I modify the schema in my codebase and test it straight away with Insomnia. Or having a keyboard shortcut so that people don't need to point-and-click to refresh their schemas (still manual but less painful). |
Ya I think a way to enable periodic refresh would be good to add back |
@gschier or maybe a keyboard shortcut for refreshing a schema might be nice to have. |
Sorry folks! This was incorrectly tagged as a feature request along with other bugs. I'm going back through and cleaning up, sorry for the inconvenience. @seanwash or @jeromedalbert if you're still looking for this enhancement, feel free to check out the Ideas in GitHub Discussions. |
Hi @rolurq |
Details
Insomnia fails to retrieve the GraphQl schema. It shows this error
I took the graphql body in the request sent by insomnia and tried it in Insomnia itself and it works.
So I guess the issue must be in the code that works with the fetched schema.
The text was updated successfully, but these errors were encountered: