-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: support other GraphQL clients by outputing to plain folders and .graphql files #28
Comments
That's a great idea, and it should be easy to do with the existing codebase! |
Actually there is also the standard that works in many clients to put informations like the URL, headers, introspection, ... in a file called Example {
"name": "GitHub GraphQL API",
"schemaPath": "schema.graphql",
"extensions": {
"endpoints": {
"https://api.github.com/graphql": {
"url": "https://api.github.com/graphql",
"headers": {
"user-agent": "JS GraphQL",
"Authorization": "bearer ${env:GITHUB_TOKEN}"
},
"introspect": true
}
}
}
} So with this we would have all the other informations from the Postman collection |
Bonjour,
I heard from graphman at https://dev.to/tristankalos/graphman-generate-a-postman-collection-for-any-graphql-endpoint-4hff
Your tool seems like something that is totally needed.
GrapphQL being a standard, I feel like it should nothing in it is specific to Postman no ?
Apart from the very last step where you store the queries in the Postman collection format.
I use https://insomnia.rest/ and the GraphQL plugin for IntelliJ
If you have an option to write the queries simply in a plain folder with plain
some-query.graphql
files, I would totally use it.The text was updated successfully, but these errors were encountered: