We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With 2.0, related .graphql files are no longer imported into the schema when we run graphql codegen. It is due to a bug that prisma-binding do not handle any import syntax at the moment. See line 73: https://github.com/prismagraphql/prisma-binding/blob/ef7fc575a8a5473db2f48574c488c71ca181bf9f/src/bin.ts#L71-L86
graphql codegen
prisma-binding
To fix it, we should wrap it with importSchema from graphql-import, i.e.
importSchema
graphql-import
return buildSchema(importSchema(input))
The text was updated successfully, but these errors were encountered:
Thanks a lot for reporting this @alvis. @timsuchanek will shortly look into this and merge your PR
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
With 2.0, related .graphql files are no longer imported into the schema when we run
graphql codegen
. It is due to a bug thatprisma-binding
do not handle any import syntax at the moment. See line 73:https://github.com/prismagraphql/prisma-binding/blob/ef7fc575a8a5473db2f48574c488c71ca181bf9f/src/bin.ts#L71-L86
To fix it, we should wrap it with
importSchema
fromgraphql-import
, i.e.The text was updated successfully, but these errors were encountered: