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
ConnectionTypeDefinitionConfigurer only considers types in the TypeDefinitionRegistry, type extensions are not considered. For example the following throws an exception on startup((The field type 'CompanyConnection' is not present when resolving type 'Query')):
extend type Query {
company(id: ID!): Company
companies(offset: Int!, limit: Int!): CompanyConnection
}
Note the extend.
Type extensions are available on the TypeDefinitionRegistry and their fields can be accessed as follows:
rstoyanchev
changed the title
Consider object extensions in ConnectionTypeDefinitionConfigurer
ConnectionTypeDefinitionConfigurer should consider object type extensions
Sep 18, 2023
ConnectionTypeDefinitionConfigurer
only considers types in theTypeDefinitionRegistry
, type extensions are not considered. For example the following throws an exception on startup((The field type 'CompanyConnection' is not present when resolving type 'Query')):Note the
extend
.Type extensions are available on the
TypeDefinitionRegistry
and their fields can be accessed as follows:The text was updated successfully, but these errors were encountered: