-
-
Notifications
You must be signed in to change notification settings - Fork 55
Warn about deprecation of old config methods instead of breaking existing code #212
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
Conversation
…y working code using the old postgres configuration methods, while setting it up so the compiler correctly defaults to the new ones in ambiguous cases.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #212 +/- ##
===========================================
- Coverage 76.55% 61.49% -15.06%
===========================================
Files 7 8 +1
Lines 354 348 -6
===========================================
- Hits 271 214 -57
- Misses 83 134 +51
|
@@ -0,0 +1,18 @@ | |||
API breakage: func DatabaseConfigurationFactory.postgres(configuration:maxConnectionsPerEventLoop:connectionPoolTimeout:encodingContext:decodingContext:sqlLogLevel:) has removed default argument from parameter 3 |
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.
Shouldn't this file be passed to the api-breakage CI using the --breakage-allowlist-path
flag (or i see there is an option for it in the reusable CI) ?
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.
Or at second glance, i think you've made the re-useable CI default to this path, so this should be no issue.
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.
The reusable breakage check option looks for a file named for the branch being checked
These changes are now available in 2.7.2 |
Previously working code which uses the now-deprecated
PostgresConfiguration
type with the.postgres
factory methods (rather than its replacement,SQLPostgresConfiguration
) while specifying neither a data encoder or decoder was throwing compiler errors. Such code now issues the intended deprecation warning instead, while continuing to work as before.Fixes #211