Skip to content

Conversation

@dannyroosevelt
Copy link
Collaborator

@dannyroosevelt dannyroosevelt commented Apr 21, 2025

WHY

Summary by CodeRabbit

  • New Features
    • Added new permanent redirects for several component-related pages to their updated locations under the contributing section. Users visiting outdated URLs will be automatically redirected to the correct pages.

@vercel
Copy link

vercel bot commented Apr 21, 2025

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

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 21, 2025 8:31pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
pipedream-docs ⬜️ Ignored (Inspect) Apr 21, 2025 8:31pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Apr 21, 2025 8:31pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 21, 2025

Walkthrough

This update modifies the Next.js configuration file for documentation by adding four new permanent redirect rules. These rules redirect specific paths under /components/ to their new locations under /components/contributing/. No other redirect or rewrite rules are changed, and there are no modifications to exported or public entities beyond the additions to the redirects array.

Changes

File(s) Change Summary
docs-v2/next.config.mjs Added four new permanent redirects from specific /components/ paths to /components/contributing/ equivalents.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Next.js Server

    User->>Next.js Server: Request /components/guidelines/
    Next.js Server-->>User: Redirect to /components/contributing/guidelines/

    User->>Next.js Server: Request /components/actions-quickstart/
    Next.js Server-->>User: Redirect to /components/contributing/actions-quickstart/

    User->>Next.js Server: Request /components/sources-quickstart/
    Next.js Server-->>User: Redirect to /components/contributing/sources-quickstart/

    User->>Next.js Server: Request /components/typescript/
    Next.js Server-->>User: Redirect to /components/contributing/typescript/
Loading

Possibly related PRs

  • PipedreamHQ/pipedream#16363: Modifies redirect rules in docs-v2/next.config.mjs for /components/ paths, addressing redirect loops and restructuring existing redirects in the same namespace.

Poem

Four new paths now leap and bound,
From components’ home to contributing ground.
Redirects in place, so users won’t stray,
Next.js guides them the right way.
With a hop and a skip, the docs stay neat—
A rabbit’s work is never complete! 🐇✨

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs-v2/next.config.mjs (1)

339-358: New component redirects are correctly added.
The four entries for /components/guidelines/, /components/actions-quickstart/, /components/sources-quickstart/, and /components/typescript/ mirror the existing redirect patterns (trailing slash, permanent: true) and point to the right targets under /components/contributing/.

Tip: these rules only catch the root pages. If you expect nested sub‑paths (e.g., /components/guidelines/intro), consider adding dynamic catch‑all redirects or consolidating into a single regex‑based rule to reduce duplication:

+      {
+        source: "/components/guidelines/:path*/",
+        destination: "/components/contributing/guidelines/:path*/",
+        permanent: true,
+      },
...

Or group all four in one rule:

{
  source: "/components/:section(guidelines|actions-quickstart|sources-quickstart|typescript)/:path*/",
  destination: "/components/contributing/:section/:path*/",
  permanent: true,
}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8c5072e and 5ad5c04.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • docs-v2/next.config.mjs (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: pnpm publish
  • GitHub Check: Lint Code Base

@dannyroosevelt dannyroosevelt merged commit 1a30a76 into master Apr 21, 2025
8 checks passed
@dannyroosevelt dannyroosevelt deleted the danny/docs-redirect-fix-again branch April 21, 2025 20:41
luancazarine added a commit that referenced this pull request Apr 28, 2025
* Adding redirects for /components child pages (#16381)

* [Components] xendit #16278
Sources
 - New Invoice

Actions
 - Create Invoice
 - Create Payout
 - Get Payment Status

* pnpm update

* some adjusts

* some adjusts

* pnpm update

* some adjusts

---------

Co-authored-by: Danny Roosevelt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants