From 26f5b45abf1caafe50df31c18e2b4d29d22f87c3 Mon Sep 17 00:00:00 2001 From: Carlos Gonzalez Date: Wed, 19 Jan 2022 22:10:27 +0200 Subject: [PATCH] Update migrating-from-v2-to-v3.md The way the function getNode is extracted on the code example is incorrect. --- docs/docs/reference/release-notes/migrating-from-v2-to-v3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/reference/release-notes/migrating-from-v2-to-v3.md b/docs/docs/reference/release-notes/migrating-from-v2-to-v3.md index 2715be78b7874..1e5125f572040 100644 --- a/docs/docs/reference/release-notes/migrating-from-v2-to-v3.md +++ b/docs/docs/reference/release-notes/migrating-from-v2-to-v3.md @@ -755,8 +755,8 @@ exports.sourceNodes = ({ actions, getNodesByType }) => { In case you only have an ID at hand (e.g. getting it from cache or as `__NODE`), you can use the `getNode()` API: ```js:title=gatsby-node.js -exports.sourceNodes = async ({ actions, getNodesByType, cache }) => { - const { touchNode, getNode } = actions +exports.sourceNodes = async ({ actions, getNode, getNodesByType, cache }) => { + const { touchNode } = actions const myNodeId = await cache.get("some-key") touchNode(getNode(myNodeId))