Stricter GraphQL typing using gatsby-plugin-typegen #1102
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hi 👋
Glad to see that the GraphQL homepage is built with Gatsby.
I set up the gatsby-plugin-typegen, which is the integration of GCG and Gatsby
All named queries are typed while gatsby develop running
Further steps
To unlock the power of GraphQL, I explored best practices while developing and using this plugin, and here are my two cents.
Nullability for implicitly inferred fields is normal. To get rid of it, we can define our model via schema customization API in gatsby-node and inject pre-transformed data.
The build-time data layer is a blessing for both development and runtime.
Colocating data dependencies using fragments is even better. just like Relay does