fix: docs update to adapte react-router link

[vkboo]

Summary by CodeRabbit

• Documentation
  • Updated URLs in the routing guide to reflect the new structure in React Router v6 documentation, ensuring links for useMatch, useLocation, useParams, and useSearchParams are accurate.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
umi	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 13, 2024 3:37pm

[coderabbitai]

Walkthrough

The update primarily focuses on correcting and updating the URLs linked to React Router v6 documentation in the routes.md file. This ensures that references are accurate and users are directed to the correct resources for better navigation and understanding of React Router functionalities.

Changes

File Path	Change Summary
docs/.../routes.md	Updated URLs for React Router v6 documentation, specifically for useMatch, useLocation, useParams, and useSearchParams.

Poem

🐰✨
In the digital fields, where code paths merge,
A little rabbit hopped, on a documentation surge.
With a twitch of his nose, and a flick of his ear,
Updated links in the docs, now crystal clear.
Hop, hop, hooray! The routes are right here! 🎉
🐾

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between a9f494a and d0e2b77.

Files selected for processing (1)

• docs/docs/docs/guides/routes.md (4 hunks)

Additional comments not posted (5)

docs/docs/docs/guides/routes.md (5)

431-431: Ensure the URL to the React Router documentation is correct and accessible.

Verification successful

---

The URL provided in the documentation for React Router v6 is correct and accessible, as confirmed by the successful HTTP status code 200 returned from the server. This verifies that the link to the React Router documentation is indeed correct and functional.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the URL is accessible
curl -o /dev/null -s -w "%{http_code}\n" https://reactrouter.com/en/main | grep 200

Length of output: 89

---

435-435: Verify the updated URL for useMatch hook points to the correct location in the React Router v6 documentation.

Verification successful

---

The URL provided in the documentation for the useMatch hook in React Router v6 has been verified to be correct and accessible, as confirmed by the successful HTTP status code 200 received from the server.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the URL is accessible and correct
curl -o /dev/null -s -w "%{http_code}\n" https://reactrouter.com/en/main/hooks/use-match | grep 200

Length of output: 105

---

456-456: Confirm the updated URL for useLocation hook is accurate and leads to the intended documentation page.

Verification successful

---

The verification script has successfully confirmed that the URL https://reactrouter.com/en/main/hooks/use-location is accessible and returns a HTTP status code of 200, indicating that the page exists and is reachable. This confirms that the updated URL for the useLocation hook in the documentation is accurate and leads to the intended documentation page.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the URL is accessible and correct
curl -o /dev/null -s -w "%{http_code}\n" https://reactrouter.com/en/main/hooks/use-location | grep 200

Length of output: 108

---

485-485: Check that the URL for useParams hook in the documentation update is correct and functional.

Verification successful

---

The URL provided in the documentation for the useParams hook (https://reactrouter.com/en/main/hooks/use-params) has been verified to be correct and functional, as it successfully returns a 200 HTTP status code, indicating that the page is accessible.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the URL is accessible and correct
curl -o /dev/null -s -w "%{http_code}\n" https://reactrouter.com/en/main/hooks/use-params | grep 200

Length of output: 106

---

500-500: Ensure the URL for useSearchParams hook is correctly updated and points to the valid documentation page.

Verification successful

---

The verification script has successfully confirmed that the URL https://reactrouter.com/en/main/hooks/use-search-params is accessible and returns a 200 HTTP status code, indicating that the page exists and is reachable. This aligns with the requirement in the review comment to ensure that the URL for the useSearchParams hook is correctly updated and points to a valid documentation page.

Based on this information, the URL provided in the documentation is correct and functional.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify the URL is accessible and correct
curl -o /dev/null -s -w "%{http_code}\n" https://reactrouter.com/en/main/hooks/use-search-params | grep 200

Length of output: 113

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.