-
Notifications
You must be signed in to change notification settings - Fork 27
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
⬆️ Fix custom settings class with pydantic-settings~=2.6
#6644
⬆️ Fix custom settings class with pydantic-settings~=2.6
#6644
Conversation
pydantic-settings==2.6.0
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## pydantic_v2_migration_do_not_squash_updates #6644 +/- ##
===============================================================================
- Coverage 71.63% 68.56% -3.08%
===============================================================================
Files 1100 963 -137
Lines 49250 43324 -5926
Branches 1390 1331 -59
===============================================================================
- Hits 35281 29703 -5578
+ Misses 13736 13385 -351
- Partials 233 236 +3
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
9aec7ae
to
a453269
Compare
Quality Gate passedIssues Measures |
pydantic-settings==2.6.0
pydantic-settings~=2.6
b01c4a7
into
ITISFoundation:pydantic_v2_migration_do_not_squash_updates
What do these changes do?
The upgrade to
pydantic-settings~=2.6
disrupted theauto_default_from_env
mechanism. This PR introduces a solution:EnvSettingsWithAutoDefaultSource
, a new settings source that executes the default factory injected upon construction of the class (see__pydantic_init_subclass__
).pydatnci-settings
everywhereRelated issue/s
How to test
Dev-ops checklist
None