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

Improve CompositeException to override getCause() #188

Merged

Conversation

cescoffier
Copy link
Contributor

@cescoffier cescoffier commented Jun 25, 2020

Improve CompositeException to override getCause (which was null initially).
It also checks that at least one exception is passed.

It might be interested later to use suppressed exceptions.

…ally).

It also checks that at least one exception is passed.

It might be interested later to use suppressed exceptions.
@cescoffier cescoffier added the enhancement New feature or request label Jun 25, 2020
@cescoffier cescoffier added this to the 0.6.0 milestone Jun 25, 2020
@jponge
Copy link
Member

jponge commented Jun 26, 2020

LGTM

@jponge
Copy link
Member

jponge commented Jun 26, 2020

Would it make sense to use suppressed exceptions for aggregating multiple exceptions?

@cescoffier
Copy link
Contributor Author

There are 2 cases, in one suppressed makes sense, but less in the other case.

If you have a failure and you react on it triggering another (unfortunate) failure, suppressed makes sense in this case. There is a "root" failure and another suppressed one.

In the other case, you have multiple failures coming from different Uni/Multi, like in a combined operation. In this case, there are no root failures, they are just a group of failures.

@cescoffier cescoffier merged commit f4f2617 into master Jun 26, 2020
@cescoffier cescoffier deleted the features/composite-exception-should-override-getCause branch June 26, 2020 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants