Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR addresses a configuration precedence issue where CLI arguments for input sources were ignored when Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Merging this PR will not alter performance
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3083 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 87 87
Lines 18247 18274 +27
Branches 2087 2089 +2
=========================================
+ Hits 18247 18274 +27
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Breaking Change AnalysisResult: No breaking changes detected Reasoning: This PR is a bug fix ensuring CLI input arguments (input, url, input_model) correctly take precedence over pyproject.toml configuration. When one of these fields is explicitly set via CLI, the others are now cleared to prevent conflicts from multiple input sources. This corrects previously broken precedence behavior (issue #3076) rather than changing intended API behavior. No CLI options, Python API signatures, defaults, generated code output, or templates are changed. Users were experiencing the buggy behavior rather than depending on it, so this is not a breaking change. This analysis was performed by Claude Code Action |
|
Hi @koxudaxi, I think this should apply to all fields, not just In general, users should be able to configure every field either through a configuration file or via CLI arguments, with CLI arguments taking precedence. |
|
@vdusek In this case, though, that already happens for normal fields. The special handling here is only for |
|
@koxudaxi Perfect, thanks for the clarification. |
|
🎉 Released in 0.56.1 This PR is now available in the latest release. See the release notes for details. |
Fixes: #3076
Summary by CodeRabbit