Docs - fix redirects

[andrewjschuang]

WHY

Summary by CodeRabbit

• New Features

  • Updated URL structure so that all paths now include a trailing slash for consistent navigation.
  • Introduced improved redirection rules ensuring outdated URLs permanently route to their new destinations.

• Chores

  • Streamlined configuration by consolidating redirection rules and removing legacy settings.

[vercel]

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

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Feb 21, 2025 7:07pm
pipedream-docs	⬜️ Ignored (Inspect)			Feb 21, 2025 7:07pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Feb 21, 2025 7:07pm

[coderabbitai]

Walkthrough

The changes update routing configurations across two files. In docs-v2/next.config.mjs, a new trailingSlash: true property and an asynchronous redirects() method are added, defining permanent URL redirection rules. Additionally, several environment variable declarations have been removed. In docs-v2/vercel.json, the redirect mappings are entirely removed, leaving only the build and install commands.

Changes

File(s)	Change Summary
docs-v2/next.config.mjs	Added trailingSlash: true property; introduced new async redirects() method with permanent redirect rules; removed environment variables.
docs-v2/vercel.json	Removed the redirects array; retained the buildCommand and installCommand entries.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant NextServer
    participant Config
    User->>NextServer: Request URL
    NextServer->>Config: Load configuration
    Config-->>NextServer: Return config (with trailingSlash & redirect rules)
    alt URL matches a redirect rule
        NextServer->>User: Redirects (301)
    else
        NextServer->>User: Serve requested page
    end

Loading

Possibly related PRs

• Docs - broken links in docs/components #14594: Introduces a similar redirect method while removing the old redirects array, indicating shifts in redirection management.
• Update quickstart.mdx #14375: Implements URL redirection adjustments that parallel the new redirects() method additions.
• Fix docs v3 redirects #13949: Modifies configuration handling for redirects, aligning with the changes in the current PR.

Suggested labels

User submitted

Suggested reviewers

• dylburger

Poem

Oh, what a hop, what a bound,
New redirects in code are found.
A configuration dance so fine,
With trailing slashes all in line.
I, the rabbit, cheer the change,
With ASCII hops across the range!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

docs-v2/next.config.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs-v2/next.config.mjs (1)

20-409: Consider centralizing or systematically generating redirect rules.
The large set of redirection rules may benefit from a more maintainable structure, such as a dedicated file or utility function to reduce the likelihood of typos and simplify updates. Additionally, consider testing for conflicting or redundant sources/destinations.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d77c967 and 5f8cffc.

📒 Files selected for processing (2)

• docs-v2/next.config.mjs (2 hunks)
• docs-v2/vercel.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• docs-v2/vercel.json

🔇 Additional comments (1)

docs-v2/next.config.mjs (1)

11-11: Confirm the impact of adding trailing slashes.
Enabling trailingSlash: true can impact SEO and break relative links if they're not consistently updated. Please verify that all references throughout the docs are compatible with trailing slash URLs.