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

Fix the content type on the wire to be consistent with the C# implemetation. #1237

Merged
merged 1 commit into from
Oct 1, 2019

Conversation

ckkashyap
Copy link
Contributor

The C# implementation expects the content-type to be called "type".

…ntation.

The C# implementation expects the content-type to be called "type"
@coveralls
Copy link

Pull Request Test Coverage Report for Build 81331

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 86.54%

Totals Coverage Status
Change from base Build 81325: 0.0%
Covered Lines: 4490
Relevant Lines: 5010

💛 - Coveralls

Copy link
Member

@DDEfromOR DDEfromOR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CK ran me through his compatibility tests. In short, the C# library uses contentType as the var name, but type as the json tag. The later has been kept to maintain backwards compatibility after I changed the var name out of a personal bias against naming something 'type'. If we touch this again I suggest TypeyMcTypeFace.

@ckkashyap ckkashyap merged commit 23aa5d0 into master Oct 1, 2019
@stevengum stevengum deleted the ckk/fixContentType branch October 24, 2019 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants