From 766c464fec8912f25067aa477e65a81b7d2c41b0 Mon Sep 17 00:00:00 2001 From: Eddy Nguyen Date: Thu, 9 Oct 2025 00:14:33 +1100 Subject: [PATCH] Update changeset to clarify upgrade path for addInterfaceFieldResolverTypes and onlyResolveTypeForInterfaces (#10463) --- packages/plugins/typescript/resolvers/CHANGELOG.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/plugins/typescript/resolvers/CHANGELOG.md b/packages/plugins/typescript/resolvers/CHANGELOG.md index 95670696ebf..3d8184040a0 100644 --- a/packages/plugins/typescript/resolvers/CHANGELOG.md +++ b/packages/plugins/typescript/resolvers/CHANGELOG.md @@ -4,7 +4,7 @@ ### Minor Changes -- [#10449](https://github.com/dotansimha/graphql-code-generator/pull/10449) [`8258f1f`](https://github.com/dotansimha/graphql-code-generator/commit/8258f1f6012c106d02ef28bca9ec424f70c4aa26) Thanks [@eddeee888](https://github.com/eddeee888)! - Add addInterfaceFieldResolverTypes option to support custom Interface resolver inheritance +- [#10449](https://github.com/dotansimha/graphql-code-generator/pull/10449) [`8258f1f`](https://github.com/dotansimha/graphql-code-generator/commit/8258f1f6012c106d02ef28bca9ec424f70c4aa26) Thanks [@eddeee888](https://github.com/eddeee888)! - Add `addInterfaceFieldResolverTypes` option to support custom Interface resolver inheritance behaviour (such as the one enabled by [makeExecutableSchema's inheritResolversFromInterfaces](https://the-guild.dev/graphql/tools/docs/generate-schema#makeexecutableschema)) ### Patch Changes @@ -30,7 +30,7 @@ - [#10218](https://github.com/dotansimha/graphql-code-generator/pull/10218) [`140298a`](https://github.com/dotansimha/graphql-code-generator/commit/140298a33b257a0b7958e361971b5bc97bbc01c2) Thanks [@eddeee888](https://github.com/eddeee888)! - Ensure Federation Interfaces have `__resolveReference` if they are resolvable entities - BREAKING CHANGES: Deprecate `onlyResolveTypeForInterfaces` because majority of use cases cannot implement resolvers in Interfaces. + BREAKING CHANGES: Deprecate `onlyResolveTypeForInterfaces` because majority of use cases cannot implement resolvers in Interfaces. Interface normal resolvers are not generated by default. Use `addInterfaceFieldResolverTypes` option released in `@graphql-codegen/typescript-resolvers@5.1.0` to support custom Interface resolver inheritance behaviour (such as the one enabled by [makeExecutableSchema's inheritResolversFromInterfaces](https://the-guild.dev/graphql/tools/docs/generate-schema#makeexecutableschema)) BREAKING CHANGES: Deprecate `generateInternalResolversIfNeeded.__resolveReference` because types do not have `__resolveReference` if they are not Federation entities or are not resolvable. Users should not have to manually set this option. This option was put in to wait for this major version. - [#10218](https://github.com/dotansimha/graphql-code-generator/pull/10218) [`140298a`](https://github.com/dotansimha/graphql-code-generator/commit/140298a33b257a0b7958e361971b5bc97bbc01c2) Thanks [@eddeee888](https://github.com/eddeee888)! - BREAKING CHANGE: Improve Federation Entity's resolvers' parent param type: These types were using reference types inline. This makes it hard to handle mappers. The Parent type now all comes from ParentResolverTypes to make handling mappers and parent types simpler.