[csharp-netcore] Propagate raw content to the ApiException error content. #4381
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.
This PR resolves an issue with the ApiException error content described in #3473 .
The issue is linked to migration to the generic
IRestResponse<T>
. The deserialization happens before the exception is actually checked byExceptionFactory
.Possible fix is to propagate both raw response content from
IRestResponse.Content
as well asIRestResponse<T>.Data
to theApiResponse
.But I think it makes sense to roll back to the older implementation, where deserialization happed if an exception hadn't been constructed.
Technical committee: @mandrean (2017/08), @jimschubert (2017/09) ❤️ @frankyjuang (2019/09)