From 73c85416f0a5bac5b9f10c8eab7aff2491dfa424 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E1=84=87=E1=85=A1=E1=86=A8=E1=84=89=E1=85=B3=E1=86=BC?= =?UTF-8?q?=E1=84=92=E1=85=AE=E1=86=AB?= Date: Wed, 20 Nov 2024 15:07:46 +0900 Subject: [PATCH] Fix a wrong link in the devtools-and-debugging docs. --- .../src/pages/learn/advanced-use/devtools-and-debugging.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/reactflow.dev/src/pages/learn/advanced-use/devtools-and-debugging.mdx b/sites/reactflow.dev/src/pages/learn/advanced-use/devtools-and-debugging.mdx index ac5bf91ae..a629dd94d 100644 --- a/sites/reactflow.dev/src/pages/learn/advanced-use/devtools-and-debugging.mdx +++ b/sites/reactflow.dev/src/pages/learn/advanced-use/devtools-and-debugging.mdx @@ -46,7 +46,7 @@ own projects and modify them to suit your needs: each component works independen ## Node Inspector -The `` component makes use of our [`useNodes`](/api-reference/hooks/use-names) +The `` component makes use of our [`useNodes`](/api-reference/hooks/use-nodes) hook to access all the nodes in the flow. Typically we discourage using this hook because it will trigger a re-render any time _any_ of your nodes change, but that's exactly what makes it so useful for debugging!