Eddy Nguyen

> Solution for me here: https://github.com/nrwl/nx/issues/10785#issuecomment-1159017136 For v14.7.5, it works for me even if I only added an empty object for `pluginsConfig` e.g. ``` // nx.json { // ... "pluginsConfig":...

Hello 👋 There was a similar [issue](https://github.com/dotansimha/graphql-code-generator/issues/9498) and here's the recommendations: https://github.com/dotansimha/graphql-code-generator/issues/9498#issuecomment-1598550662 Basically, the errors reported are from TS's `noUnusedLocals` and `noUnusedParameters` settings. It's recommended to ignore linting rules in...

Hi all 👋 Could you please try this alpha version to see if it fixes your issue: ``` @graphql-codegen/typescript-resolvers@4.0.7-alpha-20240425115511-1ac284ac51b27d312ef3f9922218f228a3b468e3 ```

Thanks for opening this issue guys 🙂 I've left the replies in the [issue opened in server preset repo](https://github.com/eddeee888/graphql-code-generator-plugins/issues/225). I'm posting the references here to make it easier: - [Reason](https://github.com/eddeee888/graphql-code-generator-plugins/issues/225#issuecomment-1968890271)...

This should be fixed in `@graphql-codegen/[email protected]`

Hi @davidgtu, Your `Scalars` type should also have input/output. For example: ```ts export type Scalars = { ID: { input: string, output: string }; String: { input: string, output: string...

Here's an example repo with codegen setup which doesn't have this issue: https://github.com/eddeee888/graphql-server-template. Please bump your package versions. I'm more than happy to re-open this issue if it's still a...

Hi @Zerebokep 👋 I'm observing the following from the sandbox: 1. The following custom config is created and passed to `scalars` option: ```ts const scalars = { ID: "string", String:...

Hi @Cliffzz, this change is intended 🙂 Can you help me understand how it breaks the GraphQL Query responses please? Best is to provide a reproduction using this [Codesandbox template](https://codesandbox.io/p/sandbox/github/dotansimha/graphql-code-generator-issue-sandbox-template/tree/master)...

Hi @Zerebokep 👋 I left a comment explaining why we moved to this approach in the new major version [here](https://github.com/dotansimha/graphql-code-generator/pull/9375#issuecomment-1603413081). I don't see us going back to maintaining both approaches...