Skip to content
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.

Sign up for GitHub

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

fix(docs): show where getNodesByType comes from #25344

Merged
merged 2 commits into from
Jul 22, 2020
Merged

fix(docs): show where getNodesByType comes from #25344

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fe8a21a
show where getNodesByType comes from
kurttomlinson Jun 27, 2020
e1bcd58
indicate the code is an example per PR feedback
kurttomlinson Jul 21, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/docs/creating-a-source-plugin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -432,7 +432,7 @@ If possible, the proactive listener approach creates the best experience if exis
The code to support this behavior looks like this:
kurttomlinson marked this conversation as resolved.
Show resolved Hide resolved

```javascript:title=source-plugin/gatsby-node.js
exports.sourceNodes = async ({ actions }, pluginOptions) => {
exports.sourceNodes = async ({ actions, getNodesByType }, pluginOptions) => {
const { createNode, touchNode, deleteNode } = actions

// highlight-start
Expand Down