-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
1.x: Deprecate CompositeException constructor with message prefix #3762
1.x: Deprecate CompositeException constructor with message prefix #3762
Conversation
We don't really use that constructor or the message, so I'd prefer removing it altogether. |
Yeah I also realized that later since no test broke after that change. So do you want me to remove it? |
Yes, but don't rush it as there is another, much heavier PR #3759 that also changed this class. |
Alright just ping me once #3759 is in |
@akarnokd I updated the PR again and changed the commit message and the title. I hope the changes are okay now. If the removal of whitespace bugs you just let me know. |
Yes, please revert those space changes. (Are you using IntelliJ?) |
Those changes I did in Sublime and I set it up in a way that it should remove trailing whitespace ;) Also updated the PR and removed the spaces |
Almost, but forgot that its a public API component thus can't just remove the constructors. Could you instead deprecate |
@akarnokd like this? |
Yes. 👍 |
👍 |
1 similar comment
👍 |
Before this PR messagePrefix was never used 💃
If you guys want I can revert the change on CompositeExceptionTest.java:177. I just thought that way it' be nicer.
About the message is there any reason for having a space after the dot?