You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: