Update dependency @eddeee888/gcg-typescript-resolver-files to v0.12.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eddeee888/gcg-typescript-resolver-files (source)	0.4.0 -> 0.12.0

---

Release Notes

eddeee888/graphql-code-generator-plugins (@​eddeee888/gcg-typescript-resolver-files)

v0.12.0

Compare Source

Minor Changes

• e84fb01: Add mappersRelativeTargetDir config option

  string (Default: ./)

  By default, mappers must be siblings with the schema they represent. For example, if the schema file is /path/to/schema.graphql, the mapper file is /path/to/schema.mappers.ts. This extension allows mappers to reside in a different directory relative to the schema file using the pattern <schemaPath>/<mappersRelativeTargetDir>/<schemaName><mappersFileExtension>.

• 221c671: Add moduleNamingMode option to determine the module name for each schema file

  • last: The module name is derived from the last directory (within the schema directory) in the file's path.
  • first: The module name is derived from the first directory (within the schema directory) in the file's path.
  • any number: The module name is derived from the nth zero-indexed directory (within the schema directory) in the file's path. Supports negative numbers which select the nth directory from the back of the file's path.

Patch Changes

• 19e1f03: Fix __resolveReference being required all the time
• b4c501c: Update internals to use faster approach to run static analysis
• df77f2e: Fix issue generated type names with custom naming convention breaks mappers static analysis
• Updated dependencies [19e1f03]
  • @​eddeee888/gcg-server-config@​0.2.3

v0.11.0

Compare Source

Minor Changes

• 9b45bf3: Use @​graphql-codegen/typescript-resolvers meta to handle federation__resolveType
• 9b45bf3: Do not add files on filesystem that have not been touched by codemod

Patch Changes

• 9b45bf3: Do not report namingConvention usage as it is fully supported

v0.10.4

Compare Source

Patch Changes

• 7f281c9: Fix scalarOverrides not giving full control to users

v0.10.3

Compare Source

Patch Changes

• de78270: Ensure __isTypeOf is in the picked properties so users can choose this way to handle abstract type should they choose

v0.10.2

Compare Source

Patch Changes

• 9088222: Fix interface mappers not being detected automatically

v0.10.1

Compare Source

Patch Changes

• 906d454: Bump @​graphql-codegen/typescript-resolvers to v4.2.1
• bb9b5fe: Use @​graphql-tools/merge to merge typeDefs
• Updated dependencies [906d454]
  • @​eddeee888/gcg-server-config@​0.2.2

v0.10.0

Compare Source

Minor Changes

• 8ec553b: Handle enum resolverGeneration, autowireup and mapper. Enable enum resolvers generation by default.
• 8ec553b: Use reported generated type names from @​graphql-codegen/typescript-resolvers meta to support all naming convention
• 8ec553b: Add fixObjectTypeResolvers.enum = smart option to ensure all allowedValues are generated
• 8ec553b: Fully support namingConvention for resolvers map

v0.9.4

Compare Source

Patch Changes

• b734d8b: Revert VariableStatement assumption that can cause runtime errors

v0.9.3

Compare Source

Patch Changes

• 386bb30: Fix issue where variable statements without type node does not get type node added
• 6715a49: Prefer detected scalar file on filesystem over scalar modules when wiring up resolvers map
• 86babc6: Fix issue where GraphQLScalarType is imported all the time, regardless of whether it's used

v0.9.2

Compare Source

Patch Changes

• 538eb24: Fix issue where whitelisted/blacklisted module can incorrectly detect extended resolvers to wire up to resolvers.generated.ts
• 263604f: Fix externalResolvers config not working for enums

v0.9.1

Compare Source

Patch Changes

• e999093: Add hooks to defineConfig context

v0.9.0

Compare Source

Minor Changes

• 454d1df: Add resolverGeneration 'minimal' mode

  minimal is the equivalent of:

  {
    "query": "*",
    "mutation": "*",
    "subscription": "*",
    "scalar": "*",
    "object": "",
    "union": "",
    "interface": ""
  }

• 454d1df: Implement file auto-wireup if detected at the right filesystem location

Patch Changes

• c48e8c6: Update internals to avoid parsing schema twice

v0.8.1

Compare Source

Patch Changes

• 3213b73: Bump base codegen plugin to apply patches from upstream
• d6df63c: Force generate object types with mappers to avoid runtime errors
• Updated dependencies [3213b73]
  • @​eddeee888/gcg-server-config@​0.2.1

v0.8.0

Compare Source

Minor Changes

• 6bf957d: Extend resolverGeneration functionality

  Allow passing in an object that to control which files to be generated. By default (i.e. resolverGeneration: 'recommended'), it's equivalent to the following settings:

  defineConfig({
    resolverGeneration: {
      query: '*',
      mutation: '*',
      subscription: '*',
      scalar: '*',
      object: '*',
      union: '',
      interface: '',
    },
  });

  Each option can take a glob pattern to tell the preset which files of a given type to be generated based on its normalized file name.

  ---

  A normalized file name has this pattern:

  <Module name>.<Top-level type name>.<Field resolver>?
  

  Consider this schema:

v0.7.5

Compare Source

Patch Changes

• 4ab8016: Use TypeScript typechecker to collect type properties

  Previously, we manually walked through the program to collect properties of types. This is problematic as there are lots of ways to declare mappers that we cannot manually handle. On top of this, type property properties can be handled natively correctly by TypeScript typechecker.

  Note: class declaration private properties are picked up by TypeScript typechecker, which could be problematic. We are keeping that case as-is.

v0.7.4

Compare Source

Patch Changes

• e909a17: fix path to output resolver files in main resolver files for nested schema files
• 067bd7e: Add params to generated resolvers
• 47c8fa6: Update package.json with missing deps
• 891f718: fix path to output resolver files so they are always generated near to schema.graphql
• b226761: Implement recursively pick interface extensions
• Updated dependencies [47c8fa6]
  • @​eddeee888/gcg-server-config@​0.1.1

v0.7.3

Compare Source

Patch Changes

• 9f3b82b: Federation support: Add __resolveReference to picked fields when extending object types

v0.7.2

Compare Source

Patch Changes

• 8ed14fc: Fix issue where dashes were not handled correctly when using extended object pattern across multiple schemas
• 7567190: Declare tslib as a dependency

v0.7.1

Compare Source

Patch Changes

• 73d9936: Relax presetConfig.typesPluginsConfig.namingConvention enforcement. Warn if used.

  In v0.7.0, we've made presetConfig.typesPluginsConfig.namingConvention to throw if used. In this release, we've relaxed it because certain options may still work e.g. upperCaseFirst . If namingConvention is used, we warn instead.

  Currently, the preset naively uses the schema type spelling/casing as the generated type. Therefore, it's important to have namingConvention option as keep. In the future, we can revisit to make sure generated resolvers have the same namingConvention support as the generated type file.

v0.7.0

Compare Source

Minor Changes

• ab6a9e7: Support extending non-root object types

  For example, given this schema:

v0.6.0

Compare Source

Minor Changes

• d0e17ad: Add resolverGeneration option

  disabled or recommended or all (Default: recommended)

  Decides which resolvers to generate:

  • disabled: generates no resolvers. Use this if you want to use your own structures. Note: if custom scalars are detected and used, resolver main files are still generated.
  • recommended: generates the minimal amount of resolvers. Use this if you want a managed experience.
    • no union/interface resolvers are generated because we rely on certain settings in typescript-resolvers that make these not required.
  • all: generates all resolvers. Use this if you want all resolvers to be generated and use the ones you need.

• 1586d73: Add missing Interface file generation

Patch Changes

• c3ee642: Fix emitLegacyCommonJSImports issues

  • Fix issue where warning always logged if presetConfig.emitLegacyCommonJSImports is used
  • Throw error when presetConfig.typesPluginsConfig.emitLegacyCommonJSImports is used
  • (Internal) Replace automatic file detection in printImportLine with 3 options: file, module and preserve:
    • This is to fix rare cases where absolute alias path is used in externalResolvers option e.g. src/module/file was missing .js because it was being detected as a module. externalResolvers is set by the user and also used internally for scalar types, so we can use preserve instead to keep the module value as-is.
    • Options:
      • file: import is a file. For ESM, .js extension is added. For CJS, no extension is added.
      • module: import is a module from node_modules or aliased e.g. graphql-scalars or @org/your-module. No extension is added.
      • preserve: preserve what the config declares. This is only used when taking user's config or preset-controlled config e.g. externalExternals because the import could be either file or module

• 191705f: Add schema option to defineConfig

• 49ba468: Added support for the case where the Type mapper is a class

• c968c2c: Fix: defineConfig's type no longer allows typesPluginsConfig.scalars or typesPluginsConfig.emitLegacyCommonJSImports

• 2205e3f: Update default custom GraphQLScalar template to guide users better

• Updated dependencies [5e58a08]

  • @​eddeee888/gcg-server-config@​0.0.1

v0.5.0

Compare Source

Minor Changes

• f7831c1: Use resolversNonOptionalTypename instead of nonOptionalTypename

  This makes using abstract types simpler because we do not return __typename for all types, only for union members and interface implementing types.

• f7831c1: Add scalarsOverrides config option

  Record<string, { resolver?: string; type?: string | { input: string; output: string } }> (Default: {})

  Overrides scalars' resolver implementation, type or both.

  Example:

  // codegen.ts
  {
    generates: {
      'src/schema': defineConfig({
        scalarsOverrides: {
          DateTime: {
            resolver: './localDateTimeResolver#Resolver',
          }
          Currency: {
            type: 'unknown'
          },
          BigInt: {
            resolver: '@​other/scalars#BigIntResolver',
            type: 'bigint'
          }
        }
      })
    }
  }

  BREAKING CHANGE: typesPluginsConfig.scalars can no longer be used. Please use scalarOverrides instead.

• f7831c1: Use optionalResolveType=true because resolversNonOptionalTypename works

• f7831c1: Add scalarsModule config option

  string or false (Default: graphql-scalars)

  Where Scalar implementation and codegen types come from. Use false to implement your own Scalars.

  If using an module that is not graphql-scalars, the module must export resolver implementation and codegen type the same way graphql-scalars does e.g.

  {
    resolvers: {
      DateTime: DateTimeResolver,
    },
    DateTimeResolver: {
      // ... resolver implementation
      extensions: {
        codegenScalarType: 'Date | string',
      },
    }
  }

Patch Changes

• f7831c1: Allows overriding native scalar types' type (Equivalent of typescript plugin's scalars option)
• f7831c1: Correctly implement ID Scalar's input/output type: input is string and output is string | number

v0.4.1

Compare Source

Patch Changes

• af10b65: Add emitLegacyCommonJSImports config option to support esm-style imports in generated output
• 72c0dc1: Fix typeDefsFileMode=modules not working well with codegen hooks (e.g. afterAllFileWrite) for Windows

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.