We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Hello. I found an issue while upgrading to springboot 3.5.0.
Springboot 3.5.0 uses graphql-java:24.0 and java-dataloader:5.0.0
With the introduction of jspecify, IDEs started throwing errors that didn't exist before.
In this version, Any? inheritance for the Value type of DataLoader is no longer available. You must explicitly inherit from Any.
Any?
Any
The current code is no longer suitable.
But, I believe that developers should be able to choose whether the result type of DataLoader is nullable or non-null.
I think graphql-java should be,
// current @NullMarked public class DataLoader<K, V> // I hope @NullMarked public class DataLoader<K, @Nullable V>
For now, I am temporarily using @Suppress("UPPER_BOUND_VIOLATED") to ignore the issue.
@Suppress("UPPER_BOUND_VIOLATED")
The text was updated successfully, but these errors were encountered:
We are facing the same issue.
Sorry, something went wrong.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Hello. I found an issue while upgrading to springboot 3.5.0.
Springboot 3.5.0 uses graphql-java:24.0 and java-dataloader:5.0.0
With the introduction of jspecify, IDEs started throwing errors that didn't exist before.
In this version,
Any?
inheritance for the Value type of DataLoader is no longer available. You must explicitly inherit fromAny
.The current code is no longer suitable.
But, I believe that developers should be able to choose whether the result type of DataLoader is nullable or non-null.
I think graphql-java should be,
For now, I am temporarily using
@Suppress("UPPER_BOUND_VIOLATED")
to ignore the issue.The text was updated successfully, but these errors were encountered: