refactor: update widget selection rules to exclude foreign key columns#1735
Conversation
Co-authored-by: Copilot <copilot@github.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 53 minutes and 51 seconds. ⌛ 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: Organization UI 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 |
There was a problem hiding this comment.
Pull request overview
This PR updates the AI-generated table widget guidance and post-processing so that widgets are not created for columns that are actual foreign keys, relying on the system’s automatic foreign-key handling instead.
Changes:
- Removed/updated prompt instructions so the AI is told not to generate widgets for columns listed under the table’s “Foreign Keys” section.
- Added a foreign-key column filter in
buildTableSettingsEntitiesto drop AI-returned widgets targeting FK columns before persisting settings.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.