fix: derive folder path from direct child for correct sorting#72
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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 |
- getFolderPath now checks direct child pages first, then recurses into subfolders using parentPath — fixes wrong path for deeply nested folder structures - Extract parentPath util to avoid duplication - Use NodeType.Page/Folder constants instead of string literals Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
724d537 to
96d7eb1
Compare
Summary
Test plan
🤖 Generated with Claude Code