-
Notifications
You must be signed in to change notification settings - Fork 181
Rename conformance tests policy validate -> custom #6356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Rename conformance tests policy validate -> custom #6356
Conversation
WalkthroughThis change renames test helper methods in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (3)📚 Learning: 2025-09-11T16:03:14.328ZApplied to files:
📚 Learning: 2025-08-28T12:52:46.927ZApplied to files:
📚 Learning: 2025-08-04T13:36:22.993ZApplied to files:
🧬 Code graph analysis (1)src/tool/subcommands/api_cmd/api_compare_tests.rs (6)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
🔇 Additional comments (5)
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 |
Codecov Report❌ Patch coverage is
Additional details and impacted files
... and 3 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
LesnyRumcajs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, my recommendation is to have a change across the board, i.e., basic -> validate_basic, validate -> validate_custom and identity to validate_identity which are a bit more expressive IMO.
Summary of changes
The conformance tests policy name "validate" is confusing. The name "custom" fits it more, and is self-explanatory.
Changes introduced in this pull request:
Other information and links
Good to have self-explanatory policies names that will match the names used in the compatibility report.
Change checklist
Summary by CodeRabbit
Note: This release contains no user-facing changes.
✏️ Tip: You can customize this high-level summary in your review settings.