You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
I would expect to be able to use fragments and the noGraphqlTag option without error.
I personally care more about reducing the repetition in my source code, and care less about reducing the size of my compiled code, thus I don't expect the generator to do anything clever in an attempt to factor out the fragments in the generated code (but if it did it would be a bonus).
Environment:
OS: macOS 10.13.6
Codegen: v0.13.0
Node: v10.11.0
Additional context
A recent comment on another issue makes me suspect that this issue is a known (but undocumented) limitation of the current implementation.
The text was updated successfully, but these errors were encountered:
Using fragments in conjunction with the
noGraphqlTag
option results in a code generation error.To Reproduce
Take any existing graphql document with fragments, and try running:
The generator produces the rather cryptic error:
Expected behavior
I would expect to be able to use fragments and the
noGraphqlTag
option without error.I personally care more about reducing the repetition in my source code, and care less about reducing the size of my compiled code, thus I don't expect the generator to do anything clever in an attempt to factor out the fragments in the generated code (but if it did it would be a bonus).
Environment:
Additional context
A recent comment on another issue makes me suspect that this issue is a known (but undocumented) limitation of the current implementation.
The text was updated successfully, but these errors were encountered: