Improve usability of response specifications #2365
Open
+1,178
−347
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.
Closes #1771
Changes:
asXyzOrFail
methods which throw exceptions for non-2xx responsesasJsonOrFail
,asJsonOrFailEither
variants to all integrationsquickRequest
now usesasStringOrFail
as the default response type.mapRight
,.orFail
toResponseAs
for better discoverability (instead of extension methods), however this causes that type parameters have to be provided explicitly sometimescc @bishabosha @lbialy