Generator does not issue errors (silences them) for the documents with syntax errors

[Mr-Goldberg]

Is your feature request related to a problem? Please describe.

When the file with `gql`` directive has a syntax error in GraphQL, the file is skipped completely from the generation process and NO ERROR GETS REPORTED.

For example, error in the word 'query' is not reported, and the whole file is skipped:

const _ContractQueries = gql`
  que ry Contracts($input: ContractConnectionInput!) {
      <some more lines>
  }
`

Describe the solution you'd like

As mentioned here, the issue can be resolved by setting noSilentErrors: true in the config file. But I don't like this solution, because the process of understanding that there's any error is very time-consuming:

1. There's no knowledge that there's an error - trying to re-generate GraphQL wrapper, restarting terminal, IDE, computer, as something might be off on my side.
2. Idea "there might be an error" - deleting the parts in the `gql`` directive to understand where the error is. After the error is found:
3. There was an error; it is the CRITICAL error (since it skips generation), but why was it not reported? And searching for the way to make the generator report errors...

It just takes time for any user to encounter it 🤷. Error reporting must be enabled by default for the errors of such magnitude.

Describe alternatives you've considered

No response

Any additional important details?

Using the latest versions of everything:

"@graphql-codegen/cli": "^6.1.1",
"@graphql-codegen/typescript": "^5.0.7",
"@graphql-codegen/typescript-operations": "^5.0.7",
"@graphql-codegen/typescript-react-apollo": "^4.4.0",

[eddeee888]

Hi @Mr-Goldberg ,

Is the suggestion here to turn on noSilentErrors: true by default?

[Mr-Goldberg]

@eddeee888 Yes

[eddeee888]

I think that makes sense 👍

Side note, I was confused how noSilentErrors: true works, as I couldn't see any difference when turning it on/off as mention here.

Now I learnt from your example that it can be used to catch errors like misspelt que ry 🙂 Thanks for that!
This will be part of the upcoming major version release (good timing!) as it's can be considered a breaking change for some users

[Mr-Goldberg]

Great! Waiting for the release 🙌