docs: split Node and Java queue API reference into folders#419
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 21 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (18)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
f96b9fe to
20a4b94
Compare
Problem
The API Reference Queue page had inconsistent structure across SDKs. The Python SDK splits its Queue reference into a nested
queue/folder (index + Job Management, Queue & Stats, Workers & Hooks, Resources & Locking, Events & Logs, Pub/Sub), giving an expandable sidebar subtree. Node and Java crammed the entire Queue API onto a single flatqueue.mdx, so their sidebars showed one entry with no sub-navigation.Fix
Restructure Node and Java to mirror the Python layout: convert each flat
queue.mdxinto aqueue/folder with the same 7-page split and ameta.jsonordering the sub-pages. A "Sub-pages" callout on each index links the subtree, matching Python.This is a pure reorganization of existing content — no API added, removed, or reworded:
/node/api-reference/queueand/java/api-reference/queuestill resolve (folder index), so all existing cross-links keep working. Java keeps itsTaskitolanding title.Pages
Both SDKs now have:
index,jobs,queues,workers,resources,events,pubsub.Verification
pnpm --dir docs lint— passpnpm --dir docs build— static export succeeds; all 14 new routes prerender, no duplicate-route warnings