You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* This may not work for cases where provided default mapper types are also nested e.g. `defaultMapper: DeepPartial<{T}>` or `defaultMapper: Partial<{T}>`.
684
685
*/
685
686
avoidCheckingAbstractTypesRecursively?: boolean;
687
+
/**
688
+
* @description If true, add field resolver types to Interfaces.
689
+
* By default, GraphQL Interfaces do not trigger any field resolvers,
690
+
* meaning every implementing type must implement the same resolver for the shared fields.
691
+
*
692
+
* Some tools provide a way to change the default behaviour by making GraphQL Objects inherit
693
+
* missing resolvers from their Interface types. In these cases, it is fine to turn this option to true.
694
+
*
695
+
* For example, if you are using `@graphql-tools/schema#makeExecutableSchema` with `inheritResolversFromInterfaces: true`,
696
+
* you can make `addInterfaceFieldResolverTypes: true` as well
0 commit comments