-
Notifications
You must be signed in to change notification settings - Fork 23
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
Query type generation fails sometimes #162
Comments
Thanks @KaiseiSato, just to confirm if this is same issue with #160 did you enable |
@cometkim |
@cometkim |
@j-yamamoto I'm not gonna fix this issue in v2 but in v3. Watch #138 for the progress. v3 fix this issue by introducing a scheduler that relies on actual schema/definitions change instead of the order of lifecycle API. I recommend that to commit and review the generated type definitions together for better DX. |
I admit it wasn't a good guide. Schema output was not stable in v2. I fixed this (and also the schema output is now stable!) in v3 and it is available in the current RC version. |
rc.0 - implemente XState based scheduler - stabilize schema output - bump GCG - upgrade yarn to v3 - rewritten core logics - upgrade eslint to v8 - upgrade plugin's dependencies - pin graphql version - rewrite emitSchema service - rewriten emitPluginDocument service - rewriten codegen service - add TS & Flow examples rc.1 - skip running on cloud build - fix config validation - more contexture reporting - turn `flattenGeneratedTypesIncludeFragments` true - stabilize documents - change maybe type to use `null` instead of `undefined` - update README rc.2 - add mdx example - MDX example to validate regression of [#117] - update dependencies - added support for `GatsbyImageData` scalar Resolves #40 Resolves #103 Resolves #104 Resolves #109 Fixes #113 Fixes #117 Fixes #120 Resolves #122 Fixes #124 Resolves #131 Fixes #139, #99 Resolves #146 Fixes #157 Fixes #159 Fixes #160 Fixes #161 Fixes #162 Resolves #168 Resolves #169 Fixes #171 [#117]: #117
Please feel free to report another issue If this is reproduced after v3 |
Overview
When running
gatsby build
, type generation sometimes fails.The output file is generated. (e.g., gatsby-types.d.ts)
I am using the Headless CMS service.
The data type definitions are always generated successfully, but the query type generation fails sometimes.
Most query types are generated correctly.
But some types are sometimes completed without being generated.
When it fails, I have confirmed that the processing order of the program is abnormal.
Source for verification
gatsby-node.ts
Result when completed correctly
Result when not completed correctly
The text was updated successfully, but these errors were encountered: