@eddeee888/gcg-typescript-resolver-files@0.12.0

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

@eddeee888/gcg-server-config@0.2.3

Patch Changes

• 19e1f03: Fix __resolveReference being required all the time

@eddeee888/gcg-typescript-resolver-files@0.11.0

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

@eddeee888/gcg-typescript-resolver-files@0.10.4

Patch Changes

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

@eddeee888/gcg-typescript-resolver-files@0.10.3

Patch Changes

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

@eddeee888/gcg-typescript-resolver-files@0.10.2

Patch Changes

• 9088222: Fix interface mappers not being detected automatically

@eddeee888/gcg-typescript-resolver-files@0.10.1

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

@eddeee888/gcg-server-config@0.2.2

Patch Changes

• 906d454: Bump @graphql-codegen/typescript-resolvers to v4.2.1

@eddeee888/gcg-typescript-resolver-files@0.10.0

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
• Use schema-ast plugin to generate a merged schema. This is a useful artifact if user needs an easy way to share the schema with another codebase or use it with libraries that support parsing only one schema file.

@eddeee888/gcg-typescript-resolver-files@0.9.4

Patch Changes

• b734d8b: Revert VariableStatement assumption that can cause runtime errors