docs: Link mapping to @link #16152
Merged
docs: Link mapping to @link #16152
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
stefanprobst
added
the
type: documentation
m-allanson
reviewed
Aug 2, 2019
| @@ -319,6 +319,10 @@ Gatsby's automatic type inference has one trick up its sleeve: for every field | |||
| that ends in `___NODE` it will interpret the field value as an `id` and create a | |||
| foreign-key relation. | |||
|
|
|||
| > Note: Before the introduction of the Schema Customization APIs in Gatsby v2.2, | |||
There was a problem hiding this comment.
I'm unsure what the takeaway is here - as a reader should this inform me that using mappings or ___NODE are equivalent, and that in both cases I can now use schema customisation instead?
There was a problem hiding this comment.
yes -- previously a plugin author would use the ___NODE naming convention to create links between nodes when creating the nodes (i.e. used by source/transformer plugins), and a user would use the mappings config key. both users and plugin authors can now use the @link extension.
There was a problem hiding this comment.
That's great - I added one more line at the end that matches your comment here
freiksenet
previously approved these changes
Aug 5, 2019
m-allanson
added
the
bot: merge on green
lipis
added a commit
to lipis/gatsby
that referenced
this pull request
Aug 5, 2019
* 'master' of github.com:gatsbyjs/gatsby: (103 commits) chore(showcase): add AntdSite (gatsbyjs#16376) docs: Fix typos in docs/blog (gatsbyjs#16366) chore(starters): add gatsby-starter-fashion-portfolio (gatsbyjs#16333) chore(showcase): Add Fourpost (gatsbyjs#16390) Docs: Fix a markdown syntax error in recipes.md (gatsbyjs#16371) docs: Update building-a-theme.md (gatsbyjs#16364) fix: update dependency @theme-ui/prism to ^0.2.29 (gatsbyjs#16385) chore: update dependency gatsby to ^2.13.51 (gatsbyjs#16375) Fix www build fix: update dependency @theme-ui/typography to ^0.2.29 (gatsbyjs#16386) fix: update dependency gatsby-plugin-theme-ui to ^0.2.29 (gatsbyjs#16387) fix: update dependency theme-ui to ^0.2.29 (gatsbyjs#16388) fix(www): fallback to github & unpkg to get README.md (gatsbyjs#16322) fix(www): replace \n into newlines for guess (gatsbyjs#16382) fix(gatsby): always use publicLoader for window.___loader (gatsbyjs#16122) feat(docs): Document what breaking changes are for themes (gatsbyjs#16302) docs: Link mapping to @link (gatsbyjs#16152) fix(gatsby): Add findMatchPath to the default loader (gatsbyjs#16334) feat(gatsby): Allow custom resolver context (gatsbyjs#16359) feat(docs): Add docs for @nodeInterface extension (gatsbyjs#16356) ...
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.
Link to creating foreign-key relations with the
@linkdirective from mappings, and vice versa.Fixes: #15816
Related: #16118, #15920