-
Notifications
You must be signed in to change notification settings - Fork 60
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
Restore exception behavior for backwards compatibility #245
Conversation
Signed-off-by: Kim Pepper <[email protected]>
Signed-off-by: Kim Pepper <[email protected]>
Signed-off-by: Kim Pepper <[email protected]>
Do we understand why these tests broke, meaning was that expected regressions? Iterate to green? |
Merge #243 on top of this and it should pass, right? |
Signed-off-by: Kim Pepper <[email protected]>
9f4e0ce
to
5255508
Compare
Signed-off-by: Kim Pepper <[email protected]>
Signed-off-by: Kim Pepper <[email protected]>
Signed-off-by: Kim Pepper <[email protected]>
I've generated the API as a separate commit so reviewers can see the changes without the noise. |
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.
I'm going to merge this and open an issue for backwards compatible exception behavior.
/** | ||
* @deprecated in 2.3.2 and will be removed in 3.0.0. | ||
*/ | ||
private bool $throwExceptions = false; |
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.
Was the old behavior true
? In which case this is the wrong default.
We need something in the user guide about error handling.
Description
In #233 we unintentionally removed the legacy exception behaviour.
This PR:
Issues Resolved
Restores the legacy exception behaviour and throws a deprecation warning when used.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.