-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Make addTypename a default transform #616
Comments
@stubailo There is just one big issue with this. When we serialize the data coming with typenames by default, mutate it via some client action e.g. using redux-form, then send it back, we still have the typenames inside the data. As our queries do not contain typenames, this fails. What is the suggest approach for fixing this? Disabling "addTypename" or adding typenames to each query? |
@swernerx if you don't use fragments, you can disable addTypename, but the easiest and most certain fix is probably to add __typename manually for the time being. |
…make mutating based on data previously queried more complex apollographql/apollo-client#616
Having the
__typename
on the client is really useful, and every spec-compliant GraphQL server is supposed to support this feature. I think we should turn on this transformation by default.This might even let us build in features that rely on the
__typename
being present.The text was updated successfully, but these errors were encountered: