feature: Exceptions should be exceptional

[jstafford5380]

Is your feature request related to a problem? Please describe.

When error codes are encountered, Refit throws. While I could catch this and handle it, the cost of the throw has already been incurred.

Describe the solution you'd like

Provide a means to handle the response without the exception being thrown. This could also open a door for project that would like to handle different codes in different ways.

Describe alternatives you've considered

Describe suggestions on how to achieve the feature

Creating an extensible response pipeline could do it. If I could insert a handler that allows me to handle the response and short-circuit the exception, that should suffice. Following a similar pattern as ASP's exception filter pipeline would feel natural, I think.

Additional context

[clairernovotny]

This could work but we'd need to have a settings configuration to control the new behavior to maintain backwards compatibility.

Open to ideas on how to architect and implement this.

[Dreamescaper]

I suggest combining it with #272 .
Add something like that to RefitSettings:
Func<HttpResponse, Exception> ExceptionFactory {get; set;}
(with default behavior provided)
And therefore throw only if this Func returns non-null result.

[StephenCleary]

Refit can wrap HttpClient, which already has a handling pipeline. Would that suit your needs?

[Dreamescaper]

@StephenCleary
You can throw custom exceptions from your HttpClientHandler, if you need, but currently there is no way to disable Refit exceptions for non-2** responses.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.