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.

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

docs(examples/usematches): Fix incorrect link in README #4170

Merged
merged 2 commits into from Sep 9, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions contributors.yml
Expand Up @@ -89,6 +89,7 @@
- davecranwell-vocovo
- DavidHollins6
- davongit
- deanmv
- denissb
- derekr
- developit
Expand Down
2 changes: 1 addition & 1 deletion examples/usematches-loader-data/README.md
Expand Up @@ -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.

Expand Down