Utilizes ApiErrorResponse<U> in all of the HTTP methods #228
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.
Hi!
This is a follow up to #219, which introduced a second type parameter used when the error response has a different structure. However, when adding types to actual API calls (HTTP methods) I noticed that this ApiErrorResponse type is not utilized.
This PR fixes it by adding a second parameter
U = T
to all HTTP method calls.All the remaining changes are style fixes introduced by linter commit hook.