-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Error when fragments are separated #528
Comments
When is this planned to release? Is there any prerelease version available |
For now, we released an alpha version with a fix for this:
|
Run into this as well but the alpha builds resolve it. Thanks. |
#559 should fix it for apollo-angular template |
Thanks for the Alpha versions. |
I only updated |
I'm getting the same issues at the moment after using the alpha to get fragments working properly. Generates fine but getting the type error as above
|
@kamilkisiela I am using |
@ganeshpms do you use |
I am also using apollo-angular, I am not doing the 'noGraphqlTag', I was getting the errors using:
|
Fixed in 0.12.0 |
@kamilkisiela , I am not using noGraphQLTag. The versions are Also, the issue #4 that I mentioned is resolved by using |
I'm getting this error. Version 1.0.6 with 1.0.6 versions of typescript and typescript-react-apollo Works
Returns
codegen.yml
Thanks for the amazing work! |
@LawJolla In 1.0.7 we fixed that, now you'll get a more readable error with the missing fragment name. |
Currently when fragments are stored separately from queries and mutations, the codegen produces a "Unknown fragment ..." error.
Example:
fragment.ts
query.ts
The text was updated successfully, but these errors were encountered: