-
Notifications
You must be signed in to change notification settings - Fork 5
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
Naming issues with custom Query root type #75
Comments
Thanks for reporting! Could you share the configuration you are using with |
Its implicitly included in the client preset |
I was able to reproduce this issue with: query CustomQuery {
...
}
schema {
query: CustomQuery
} I'm looking into it and will let you know once the fix is released 👌 |
@eliasdarruda this is now fixed as of v1.2.1. Feel free to give it a go and let me know if you're facing any other issues when using it with the client presets and hasura 😉 |
Thanks a lot! it worked |
I think there is a issue when the __typename doesnt follow the "Query" or "Mutation" pattern
Testing the following query (querying through hasura)
typescript-operations
generates for me:What
graphql-codegen-factories/operations
generates for me is:The expected output here should be:
Here is what I'm using for my
codegen.ts
file:The text was updated successfully, but these errors were encountered: