Add GenerateConfig lazy import from top-level module#2961
Conversation
|
Warning Rate limit exceeded@koxudaxi has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 58 seconds before requesting another review. ⌛ 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. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
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 |
|
📚 Docs Preview: https://pr-2961.datamodel-code-generator.pages.dev |
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 #2961 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 94 94
Lines 17738 17759 +21
Branches 2038 2038
=========================================
+ Hits 17738 17759 +21
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:
|
23d5e26 to
0f79b4d
Compare
Generated by GitHub Actions
Breaking Change AnalysisResult: No breaking changes detected Reasoning: This PR is purely additive - it adds a new convenience import path for GenerateConfig from the top-level module (from datamodel_code_generator import GenerateConfig). The existing import path (from datamodel_code_generator.config import GenerateConfig) continues to work exactly as before. While the new top-level import raises ImportError in Pydantic v1 environments, this is expected behavior for a new feature that requires Pydantic v2, not a change to existing functionality. No existing code will break as a result of this change. This analysis was performed by Claude Code Action |
|
🎉 Released in 0.53.0 This PR is now available in the latest release. See the release notes for details. |
Related: #1160 (reply in thread)