Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Utilizes ApiErrorResponse<U> in all of the HTTP methods #228

Conversation

rszalski
Copy link
Contributor

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.

@robinheinze
Copy link
Member

Thanks @rszalski! We had another PR merged yesterday which fixed the same linter issues, so there are some conflicts now. If you get those fixed up, we can merge this!

@rszalski
Copy link
Contributor Author

@robinheinze done! Should be all good now :)

@robinheinze robinheinze merged commit 94dedd7 into infinitered:master Sep 17, 2019
infinitered-circleci pushed a commit that referenced this pull request Sep 17, 2019
## [1.1.1](v1.1.0...v1.1.1) (2019-09-17)

### Bug Fixes

* **ts-params:** Utilizes ApiErrorResponse<U> in all of the HTTP methods ([#228](#228)) ([94dedd7](94dedd7))
@infinitered-circleci
Copy link

🎉 This PR is included in version 1.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@rszalski rszalski deleted the feature/add_apiresponse_error_to_http_methods branch September 17, 2019 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants