-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect arguments to Assert.isInstanceOf in AnnotatedControllerConfigurer #282
Comments
For reference: As a workaround I am defining the @Bean
fun annotatedControllerConfigurer(): AnnotatedControllerConfigurer? {
return AnnotatedControllerConfigurer()
} |
Could you tell us which Spring for GraphQL and Spring Boot versions are you using to reproduce that? |
I am using Spring Boot 2.6.3 and Spring for GraphQL 1.0.0-M5 |
I see - those are incompatible versions. You can get a default setup with start.spring.io (by selecting the latest 2.7.x milestone or snapshot). |
Thats fine. I take that note. But did you actually look at the linked line in the code? I am quite convinced, that there is an issue anyway. This issue is not raised from version incompatibility. Here is another use of Line 115 in 5ff3f8b
In other words: This issue will persist in Spring Boot 2.7.0-M1 and 3.0.0-SNAPSHOT |
This appears to be an issue with the Assert arguments indeed. |
@rstoyanchev @bclozel Thank you very much for looking into this. best regards |
Hi there,
first of all thank you for your awesome work. I noticed a potential bug on the M5 release of spring-boot-graphql. Upon launching my application the exception "Object of class [java.lang.String] must be an instance of class org.springframework.format.support.FormattingConversionService" occurs.
After a bit of digging in the code I noticed a potential bug in the following line:
spring-graphql/spring-graphql/src/main/java/org/springframework/graphql/data/method/annotation/support/AnnotatedControllerConfigurer.java
Line 135 in 0b449d8
I am no expert in this by all means, but isn't the second argument of the assert the actual object to check? Thus passing the message as the second argument would raise the exception shown above.
It was introduced with 0b449d8 to fix #271.
The text was updated successfully, but these errors were encountered: