Skip to content
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

Merged
merged 1 commit into from
Mar 23, 2016
Merged

1.x: Deprecate CompositeException constructor with message prefix #3762

merged 1 commit into from
Mar 23, 2016

Conversation

vanniktech
Copy link
Collaborator

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?

@akarnokd
Copy link
Member

We don't really use that constructor or the message, so I'd prefer removing it altogether.

@vanniktech
Copy link
Collaborator Author

Yeah I also realized that later since no test broke after that change. So do you want me to remove it?

@akarnokd
Copy link
Member

Yes, but don't rush it as there is another, much heavier PR #3759 that also changed this class.

@vanniktech
Copy link
Collaborator Author

Alright just ping me once #3759 is in

@vanniktech vanniktech changed the title Fix messagePrefix in CompositeException Remove messagePrefix from CompositeException Mar 17, 2016
@vanniktech
Copy link
Collaborator Author

@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.

@akarnokd
Copy link
Member

Yes, please revert those space changes. (Are you using IntelliJ?)

@vanniktech
Copy link
Collaborator Author

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

@akarnokd
Copy link
Member

Almost, but forgot that its a public API component thus can't just remove the constructors. Could you instead deprecate CompositeException(String message, List<Throwable> errors)?

@vanniktech
Copy link
Collaborator Author

@akarnokd like this?

@akarnokd
Copy link
Member

Yes.

👍

@vanniktech vanniktech changed the title Remove messagePrefix from CompositeException 1.x: Deprecate CompositeException constructor with message prefix Mar 19, 2016
@artem-zinnatullin
Copy link
Contributor

👍

1 similar comment
@stevegury
Copy link
Member

👍

@akarnokd akarnokd merged commit 8611671 into ReactiveX:1.x Mar 23, 2016
@vanniktech vanniktech deleted the dev_fix_composite_exception_message_prefix branch March 23, 2016 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants