Issue 36 http response headers #38
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…addition to the JsonContent returned. Reworking all endpoints to use SteamWebResponse. Reworking unit tests as necessary. Reworking automapping as necessary.
Prevent multiple auto mapper initialization. Fixed bug with match first blood time data type.
Fixed auto mapping configurations based on validations. Fixed unit tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds support for viewing HTTP headers in the response of every endpoint. I've implemented in such a way as to be "agnostic" to HTTP. Instead of returning an HttpResponseMessage directly, I abstract that away using a SteamWebResponse object.
I've also adjusted auto mappings, unit tests, and comments based on the changes.