This repository was archived by the owner on May 3, 2022. It is now read-only.
Default to sending Accept and Content-Type headers for json#12
Merged
Default to sending Accept and Content-Type headers for json#12
Conversation
Contributor
Author
|
@bryanmacfarlane This is ready for review now |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Sending Content-Type / Accept : application/json headers by default when using
<verb>Json<T>()helpers, if the header is not set in the client properties or passed into the functionBumps version to 1.0.6, and inverts the RELEASES document to make it easier to read (most recent at top vs bottom)