From 2a22a0f36638fa9c1c27580896cdd42d88a7d96d Mon Sep 17 00:00:00 2001 From: Deanmv Date: Fri, 9 Sep 2022 21:16:30 +0100 Subject: [PATCH] docs(examples/usematches): Fix incorrect link in README (#4170) --- contributors.yml | 1 + examples/usematches-loader-data/README.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/contributors.yml b/contributors.yml index 169cb7176d3..bc19804e993 100644 --- a/contributors.yml +++ b/contributors.yml @@ -89,6 +89,7 @@ - davecranwell-vocovo - DavidHollins6 - davongit +- deanmv - denissb - derekr - developit diff --git a/examples/usematches-loader-data/README.md b/examples/usematches-loader-data/README.md index 417a4cddd6e..e712ab9b955 100644 --- a/examples/usematches-loader-data/README.md +++ b/examples/usematches-loader-data/README.md @@ -20,7 +20,7 @@ You can further build custom hooks (`useProjects`, `useUser`, etc.) around the ` No need to use global React contexts anymore to access your React state. - Check out the [useMatchesData](app/useMatchesData.ts) implementation to see how we use `useMatches`. -- Check out the [useOptionalUser](app/useOptionalUser.ts) implementation to see how to implement `useMatchesData` internally in custom hooks. +- Check out the [useOptionalUser](app/useUser.ts) implementation to see how to implement `useMatchesData` internally in custom hooks. - Check out the [root](app/root.tsx) loader function, to see that we use loaders to return json data server-side for our routes. - Check out the [index](app/routes/index.tsx) route, as an example for how to access loader data of parent and child routes across our application with our custom hooks.