Upgrading from old graphql-codegen version with different resolver structure

[h-davis-aqovia]

I am upgrading from a v1 of version of graphql-codegen. The structure and names of resolvers is a lot different. I understand the preset is opinionated like that but is there anyway to specify naming structure?

I currently have this structure throughout:

entities/company/Company.schema.graphql
entities/company/resolvers/Company.ts (object resolvers)
entities/company/resolvers/Mutation.ts
entities/company/resolvers/Query.ts

It does not seem to be able to see query or mutation resolvers that do not follow the modern structure (e.g. company/resolvers/Query/company.ts)

resolvers.generated.ts

`/* This file was automatically generated. DO NOT UPDATE MANUALLY. */

import    { Company } from './../entities/Company/resolvers/Company';

    export const resolvers: Resolvers = {
      Company: Company,
    }`

config.yml

`schema: '**/*.graphql'
 generates:
  graphql/generated:
    preset: '@eddeee888/gcg-typescript-resolver-files'
    watchPattern: '**/*.mappers.ts'
    presetConfig:
      typesPluginsConfig: 
        enumsAsTypes: true
        declarationKind: interface
        dedupeOperationSuffix: true
        immutableTypes: true
        namingConvention: keep
        noSchemaStitching: true
        operationResultSuffix: Data
        optionalResolveType: true
        useIndexSignature: true`

[eddeee888]

Hi @h-davis-aqovia ,
There are some options such as moduleNamingMode to tweak the folder structures, however, it is not fully flexible yet.

However, most likely the requirement of root-level resolver being split will be there for the long term.
i.e. entities/company/resolvers/Mutation.ts and entities/company/resolvers/Query.ts may need migration

If you'd like to do entity-by-entity migration, whitelistedModules and blacklistedModules are useful options to use 🙂

Let me know if there's anything else I could help with!