Refit interface methods that return Task<IApiResponse> assign ApiException to the IApiResponse.Error property on error #1290
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Refit interface methods that return
Task<IApiResponse>
throwApiException
on error, rather than assigning it to theIApiResponse.Error
property (like what happens forTask<IApiResponse<T>>
orTask<ApiResponse<T>>
). See #1289 for more details.What is the new behavior?
Refit interface methods that return
Task<IApiResponse>
will assignApiException
to theIApiResponse.Error
property on error rather than throw it.What might this PR break?
Consumers that rely on the old undocumented behavior of
ApiException
being thrown from Refit interface methods that returnTask<IApiResponse>
.Please check if the PR fulfills these requirements