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

Sync-Up With graph-gophers/graphql-go(Fork's) Master #1

Open
wants to merge 97 commits into
base: fix-resp
Choose a base branch
from

Conversation

abhif22
Copy link

@abhif22 abhif22 commented Aug 21, 2019

Last Sync-Up occurred on Aug 6, 2018. This PR is for syncing up with latest(Jul 25, 2019).
Changes

  1. Pulled Latest Commit from graphql-go master (Support for Subscriptions was added by them in latest commits).
  2. [Background] Our Gqlserver's implementation adds a custom error handling for queries/mutations. This method led to new commits for subscription giving build errors in our gqlserver. So we had to add this custom error handling in Subscription related changes also. Refer this line.
    d69a0b9#diff-47a7942f5c3771dc4c337e572574277eL32

Note: We are trying to merge this PR into fix-resp since we are using fix-resp branch as dependency for gqlserver (https://github.com/tokopedia/graphql-go/releases/tag/v1.2)

matiasanaya and others added 30 commits May 12, 2018 07:09
…e has an error

Signed-off-by: Kirill Danshin <k@guava.by>
Prior to the fix, the new TestNilInterface test would fail with:

  graphql: panic occurred: reflect: Method on nil interface value
…l-panic

panic message should me meaningful: invalid type should say which typ…
reverse order of errors vs data in response
Properly handle nil interface resolvers
This benchmark was used to justify a tiny change in graph-gophers#218. Now that we all know
the joys of fmt.Stringer, I don't see any reason to keep this file around,
especially in the root package.
pavelnikolov and others added 27 commits January 8, 2019 23:36
Validate types are including all fields from implemented interface(s)
Use Struct Field Resolver instead of Method
Implement error propagation on non-null fields
Allows the server to disable schema introspection.
Add DisableIntrospection SchemaOpt
Moving package globals to per-schema objects, resolving data races from
 parsing multiple schemas in parallel. While this has limited likelihood
 in production code (since typically just 1 schema would be used), tests
 are a different story
Validating enum values supplied via variable input, and those returned
 from resolvers, ensuring that only valid enum values defined by the
 GraphQL schema are accepted
…on-schema-parsing

Resolve schema parsing data races
Introspection via ToJSON works differently when used via the
 `Schema.ToJSON` function than when making an introspection query from a
 client such as GraphiQL. In the later case, introspection uses the
 Schema's registered resolver, while in the former case, a
 `resolvable.Schema` is faked

Without the `Meta` being set on this `resolvable.Schema` (following the
 recent changes to address race conditions around the Meta schema), this
 resulted in a panic when using this form of schema introspection.
…ntrospection-tojson

Fix Panic on Introspection of Schema using ToJSON
Validating Input values supplied via variable input are supplied with
 the correct input structure and values. This includes ensuring that
 enum embedded within input values are validated as well
Adding example app that allows responses to be cached based on hints
 added to the request context by resolvers. HTTP Cache-Control header
 is added using a customised version of the `relay` package HTTP handler
 implementation
@abhif22 abhif22 changed the title Trying subscription Sync-Up With graph-gophers/graphql-go(Fork's) Master Aug 22, 2019
@abhif22 abhif22 changed the base branch from master to fix-resp August 22, 2019 05:27
@iwanbk
Copy link

iwanbk commented Aug 26, 2019

Refer this line.
d69a0b9#diff-47a7942f5c3771dc4c337e572574277eL32

as far as I can see, this is your only commit, CMIIW as I only checked this commit.

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.