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

Consider alternative approach to registered framework exceptions that would allow more flexibility #12

Open
CoolDadTx opened this issue May 5, 2018 · 0 comments

Comments

@CoolDadTx
Copy link
Owner

Currently the registered exceptions only impact whether an exception is ignored when GetRootException is called. Consider making this more flexible such that it would be possible to return different exceptions instead.

Use Case: If HttpClient returns back a HttpResponseException and the status code is 400 and the error response type is a bad argument then return ArgumentException instead.

Concerns: Stack trace needs to be rebuilt. Ideally should not be very expensive. Still will want to ignore some exceptions or unwrap others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant