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
@GraphQlRepository
public interface PetRepository extends JpaRepository<Pet, Long>, QuerydslPredicateExecutor<QPet> {
}
AR: Spring GraphQL unable to handle petList query.
Perhaps, GraphQL type is not resolved correctly in org.springframework.graphql.data.query.AutoRegistrationRuntimeWiringConfigurer.AutoRegistrationWiringFactory#getOutputTypeName.
The text was updated successfully, but these errors were encountered:
The Java type name QPet doesn't match the GraphQL type name Pet, so auto-registration won't match them for use with Querydsl. However, it should match the Pet from JpaRepository for use with Query By Example.
I think there is indeed an issue with a not null list specifically, which should be fixed in 1.2 snapshots as a result of a recent change. However, it needs to be backported to 1.1. Can you confirm it does work if the list is nullable?
rstoyanchev
changed the title
@GraphQlRepository doesn't work for not null list result
Auto-registration of @GraphQlRepository doesn't work if the returned list is declared not null
Apr 12, 2023
Example query:
Data Repository:
AR: Spring GraphQL unable to handle
petList
query.Perhaps, GraphQL type is not resolved correctly in
org.springframework.graphql.data.query.AutoRegistrationRuntimeWiringConfigurer.AutoRegistrationWiringFactory#getOutputTypeName
.The text was updated successfully, but these errors were encountered: