Bug: Fails on save when fragment is in separate .graphql file

[ntziolis]

Setup:

• .graphql A contains fragment B
• .graphql file C contains a an operation that references the fragment B

Result:

• The extension works without issues when saving A
• The extension reports a failure when saving B
  • "Codegen threw 3 errors, first one: GraphQL Document Validation failed with 1 errors; Error 0: GraphQLDocumentError: Unknown fragment"

Note:
When running the codegen manually the generation succeeds without issues.

Plugins used:

• typescript
• typescript-operations
• typed-document-node
• typescript-apollo-angular

This extension is immensely helpful, we are happy to assist in any way we can to resolve this issue. In the meanwhile any workaround to get this working would be highly appreciated.

[capaj]

I would be open to merging a PR which would resolve this.
I think an easy workaround would be to enable loading of all files when usage of fragment from another file is detected.
Even easier would be a config switch that would force all files to load for each generation.

I don't have capacity right now, but I may get to it at the end of the year if no one beats me to it.