You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current generation tool relies on executing a query on the target API endpoint. This may cause authentication issues, rate limiting etc.
Describe alternatives you've considered
Switching library, using other tool for generating the code, host the schema to use existing functionality requiring the endpoint to be active.
Additional context
The text was updated successfully, but these errors were encountered:
Could you explain why authentication is an issue? I understand that this feature would be great, but at the same time, I don't see how it is blocking anyone. We support authentication and rate-limiting shouldn't be an issue. Maybe I am missing something ...
I'll agree with @AlexGustafsson that this feature would be good to have.
We generate our schema from the server-side as a JSON file that can then be used by the client(s) instead of forcing us to temporarily host the dev server (for example) for the tool to fetch it and then shut it down. Some might not even be able to run the dev server, actually. So this is my main reason. Less friction in the team.
+1 for schema generation from a local file (even GraphQL is fine for our use-case).
During local development, we can often get rate-limited from the backend. Being able to generate from a locally available schema file is very convenient.
Is your feature request related to a problem? Please describe.
The current generation tool relies on executing a query on the target API endpoint. This may cause authentication issues, rate limiting etc.
Describe the solution you'd like
I'd like to be able to generate a tool based on provided JSON data, such as GitHub's official GraphQL API schema: https://github.com/octokit/graphql-schema/blob/master/schema.json.
Describe alternatives you've considered
Switching library, using other tool for generating the code, host the schema to use existing functionality requiring the endpoint to be active.
Additional context
The text was updated successfully, but these errors were encountered: