fix(dashboard): section detail 404 (wrong engine path)#10
Conversation
The section-detail API route forwarded to /v1/documents/{docId}/sections/
{id}, which the engine does not expose (it only has the flat
/v1/sections/{id}, scoped by the org header). Every section-detail view
returned 'Section not found'. Point it at the correct endpoint.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Warning Review limit reached
Next review available in: 49 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 (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
The section-detail route forwarded to
/v1/documents/{docId}/sections/{id}— a path the engine doesn't have (it only exposes the flat/v1/sections/{id}, scoped by the org header). Every 'view section' returned Section not found. Fixed to the correct endpoint.Note: two sibling routes hit the same class of bug and are also 404ing against the engine —
/v1/documents/{id}/toc(playground) and/v1/documents/{id}/sections/batch. Those need response-shape mapping to/treeand are a separate follow-up.