4 ms·
Have you found a way to get build errors with GraphQL queries? I only ever get them during runtime when the request is made, I assume because that's the point
by SketchySeaBeast 5y ago
Have you found a way to get build errors with GraphQL queries? I only ever get them during runtime when the request is made, I assume because that's the point at which the back-end and front-end disagree on what you're requesting.
- potatoz2 5y agoIf you generate types from your GraphQL queries, they are validated against the schema at that time (so you'd get schema errors then, of course there can still be network errors, server errors or user/semantic errors at runtime)
- nawgz 5y agoUsing Typescript,GraphQL-codegen, and Hasura, I can build correct-by-construction React apps. GraphQL-codegen & Hasura introspect the DB to type the query result, and typescript confirms my JS is not accessing any of those fields illegally. It’s pretty killer to open GraphiQL, write a new query, drop it into a graphql file in my repo, rerun the codegen, and be able to have type safe operations on the queried data. Also makes me completely unsure why anyone would want what the OP is but that’s ok
- atom_arranger 5y agoThis solution seems to work like this: - Generate type safe client based on your schema. - Access GraphQL properties as if they were just JS object properties. So in this solution the codegen step comes before writing a query. You get the same advantages pretty much, and you have less likelihood of querying for unused data.