Apollo-client: Make addTypename a default transform
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.
stubailo
All 3 comments
stubailo
on 6 Sep 2016
@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
on 9 Dec 2016
@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.
helfer
on 13 Dec 2016
Related issues
MichaelDeBoey
路
3Comments
nicolasxu-bg
路
3Comments
rafgraph
路
3Comments
dispix
路
3Comments
joergbaier
路
3Comments
Most helpful comment
@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?