-
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
[BUG] Regression in default exception behavior #250
Comments
@dblock I went with this approach originally, but since all creation of the 2.3.x |
@kimpepper Am I misunderstanding and the default with the
If this is the case we just need better docs explaining that |
Looks like I missed that step. I created #251 |
What is the bug?
In #245 we may have flipped the default exception behavior. That should be undone. We also need notes in UPGRADING and a section in the user guide on how to handle errors without exceptions.
What is the expected behavior?
Backwards-compatible behavior in 2.4.0, breaking change in 3.0.
The text was updated successfully, but these errors were encountered: