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
I am using GraphQL Code Generator to generate a Typescript typed client. This works great if I point my codegen schema file at the deployed subgraph, i.e.
Failed to load schema from ../subgraph/schema.graphql:
Unknown type: "BigInt".
Error: Unknown type: "BigInt"
Some helpful people on Discord informed me that the schema that Graph uses is non-compliant and therefore shouldn't be treated as such. However, with the wealth of tooling for GraphQL, it would be really nice to get the generated schema that is compliant.
The text was updated successfully, but these errors were encountered:
Thanks for the write-up: The current problem is that we use schema.graphql as our database schema definition. The actual generated schema that clients query is not saved during development process. I see two milestones to solve this problems:
Low hanging fruit: Make yarn build also output the generated schema so we can reuse it for tooling like that
Longterm: Refactor the database schema definition into its own DSL like Prisma Schema. Although this needs more discussion.
I am using GraphQL Code Generator to generate a Typescript typed client. This works great if I point my codegen schema file at the deployed subgraph, i.e.
However if I try to point at a local schema, i.e.
I get an error about types:
Some helpful people on Discord informed me that the schema that Graph uses is non-compliant and therefore shouldn't be treated as such. However, with the wealth of tooling for GraphQL, it would be really nice to get the generated schema that is compliant.
The text was updated successfully, but these errors were encountered: