Add fixt.co to readme #84
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
|
Congrats on the launch! |
ChristopherBiscardi
added a commit
to ChristopherBiscardi/gatsby
that referenced
this pull request
Jun 9, 2019
The parent child warnings described in gatsbyjs#83 were the result of us trying to stuff fileNode into Mdx graphql types. As it turns out, this is not necessary because you can query the parent using fragments which more accurately reflect the existence or non-existence of parent types. This also means you could query the base contentful/remote CMS types when trying to add slug fields, etc. Additionally, we unified the code paths that create nodes for all sources and transformers. Since we now use the public APIs, we can have more confidence that people can do everything we can in core when creating new content types.
ChristopherBiscardi
added a commit
to ChristopherBiscardi/gatsby
that referenced
this pull request
Jun 27, 2019
The parent child warnings described in gatsbyjs#83 were the result of us trying to stuff fileNode into Mdx graphql types. As it turns out, this is not necessary because you can query the parent using fragments which more accurately reflect the existence or non-existence of parent types. This also means you could query the base contentful/remote CMS types when trying to add slug fields, etc. Additionally, we unified the code paths that create nodes for all sources and transformers. Since we now use the public APIs, we can have more confidence that people can do everything we can in core when creating new content types.
johno
pushed a commit
to johno/gatsby
that referenced
this pull request
Jul 17, 2019
The parent child warnings described in gatsbyjs#83 were the result of us trying to stuff fileNode into Mdx graphql types. As it turns out, this is not necessary because you can query the parent using fragments which more accurately reflect the existence or non-existence of parent types. This also means you could query the base contentful/remote CMS types when trying to add slug fields, etc. Additionally, we unified the code paths that create nodes for all sources and transformers. Since we now use the public APIs, we can have more confidence that people can do everything we can in core when creating new content types.
pragmaticpat
pushed a commit
to pragmaticpat/gatsby
that referenced
this pull request
Apr 28, 2022
v2 deps update
This was referenced Nov 9, 2022
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.
No description provided.