docs: add --timeout option to create-prd and cleanup sidebar#54
Conversation
- Added --timeout, -t option documentation for PRD creation - Added examples for disabling timeout (--timeout 0) - Removed non-functional search placeholder from sidebar - Made version badge dynamic using npm_package_version env var
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughThe pull request updates the sidebar component to dynamically display version information from build-time environment variables instead of hardcoded values, and adds documentation for a new --timeout CLI option for the create-prd command with configurable AI agent call timeouts. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@website/components/docs/Sidebar.tsx`:
- Around line 14-18: The client component Sidebar.tsx currently reads
process.env.npm_package_version in the const version, which is undefined in
browser builds; fix by exposing the version to the client: either set a
NEXT_PUBLIC_VERSION env var and replace process.env.npm_package_version with
process.env.NEXT_PUBLIC_VERSION (or inject NEXT_PUBLIC_VERSION at build), or
move the version resolution out of the 'use client' Sidebar into a server
component/page that reads process.env.npm_package_version (or next.config.mjs
env) and pass the resolved version down to Sidebar via a prop named version;
update references to the const version in Sidebar to use the passed prop if you
choose the server-prop approach.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
website/components/docs/Sidebar.tsxwebsite/content/docs/cli/create-prd.mdx
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{js,ts,jsx,tsx}
📄 CodeRabbit inference engine (CLAUDE.md)
Start all code files with a file-level JSDoc comment section explaining the file's purpose, prefixed with 'ABOUTME: '
Files:
website/components/docs/Sidebar.tsx
**/*.{js,ts,tsx,jsx}
📄 CodeRabbit inference engine (AGENTS.md)
Start all code files with a file-level JSDoc comment section explaining the file's purpose, prefixed with "ABOUTME: "
Files:
website/components/docs/Sidebar.tsx
🔇 Additional comments (4)
website/components/docs/Sidebar.tsx (2)
1-5: ABOUTME comment present and compliant.The file-level JSDoc comment correctly explains the file's purpose with the required
ABOUTME:prefix. As per coding guidelines, this is compliant.
101-101: Version interpolation looks correct.The template literal syntax for displaying the version is appropriate, assuming the version constant is correctly populated.
website/content/docs/cli/create-prd.mdx (2)
33-33: Option documentation is clear and complete.The
--timeoutoption is well-documented with both short (-t) and long (--timeout) flags, units (milliseconds), default value (180000), and the special case (0 = no timeout).
68-76: Examples section is helpful and well-structured.The "Disable Timeout" section provides practical examples with inline comments explaining the values. The 10-minute example with
600000milliseconds and the explanatory comment is particularly helpful for users unfamiliar with millisecond conversions.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
The previous approach using process.env.npm_package_version failed because that env var is only available in Node.js builds, not the browser client bundle. This fix: - Reads version from package.json in next.config.mjs - Exposes it via the env config as NEXT_PUBLIC_VERSION - Sidebar now uses process.env.NEXT_PUBLIC_VERSION (safe for client)
…eanup docs: add --timeout option to create-prd and cleanup sidebar
Summary
Documentation updates for the create-prd command and sidebar improvements:
Added --timeout option documentation
--timeout, -t <ms>option in create-prd command--timeout 0)Removed non-functional search placeholder
Made version badge dynamic
npm_package_versionenvironment variableSummary by CodeRabbit
New Features
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.