-
Notifications
You must be signed in to change notification settings - Fork 60
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
feature: Adds support for GraphQL over HTTP media type #558
Conversation
✅ Docs Preview ReadyNo new or changed pages found. |
✅ Deploy Preview for apollo-ios-docc canceled.
|
✅ Deploy Preview for eclectic-pie-88a2ba ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Done. |
|
||
// This test is odd because you might assume it would fail but there is no content-type checking on standard | ||
// GraphQL response parsing. So this test is here to ensure that existing behaviour does not change. | ||
func test__response__givenUnknownContentType_shouldNotFail() throws { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added tests to keep the existing behaviour of standard GraphQL response parsing including this odd one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests all look good. I just thing that we should clean the repeated string constants up with a helper method.
78085ef
to
179d004
Compare
@AnthonyMDev - this PR is ready for another review, I've addressed the previous comment. |
ee597100 feature: Adds support for GraphQL over HTTP media type (#558) git-subtree-dir: apollo-ios git-subtree-split: ee59710005066e0f9516730a64eb800d8486a74a
…HTTP media type git-subtree-dir: apollo-ios git-subtree-mainline: b7ef8e6 git-subtree-split: ee59710005066e0f9516730a64eb800d8486a74a
Closes apollographql/apollo-ios#3485.
application/json
. Instead it simply attempts to deserialize anything as if it is JSON. It's only in the multipart parsers that we do a content type check for the chunks. @AnthonyMDev - this hasn't been an issue for now but do you think we should add this check? I'm inclined to leave the standard parser as it is.