-
Notifications
You must be signed in to change notification settings - Fork 682
Custom Repository returns Optional
as return type for T
#3125
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
Comments
This is a bug in our |
Optional
as return type for T
mp911de
added a commit
that referenced
this issue
Jul 23, 2024
… method post-processing. We now consider the declaring class to properly resolve type variable references for the result post-processing of a query method result. Previously, we attempted to resolve the return type without considering the actual repository class resolving always Object instead of the type parameter. Closes #3125
mp911de
added a commit
that referenced
this issue
Jul 23, 2024
… method post-processing. We now consider the declaring class to properly resolve type variable references for the result post-processing of a query method result. Previously, we attempted to resolve the return type without considering the actual repository class resolving always Object instead of the type parameter. Closes #3125
mp911de
added a commit
that referenced
this issue
Jul 23, 2024
… method post-processing. We now consider the declaring class to properly resolve type variable references for the result post-processing of a query method result. Previously, we attempted to resolve the return type without considering the actual repository class resolving always Object instead of the type parameter. Closes #3125
mp911de
added a commit
that referenced
this issue
Jul 23, 2024
… method post-processing. We now consider the declaring class to properly resolve type variable references for the result post-processing of a query method result. Previously, we attempted to resolve the return type without considering the actual repository class resolving always Object instead of the type parameter. Closes #3125
mp911de
added a commit
that referenced
this issue
Jul 23, 2024
… method post-processing. We now consider the declaring class to properly resolve type variable references for the result post-processing of a query method result. Previously, we attempted to resolve the return type without considering the actual repository class resolving always Object instead of the type parameter. Closes #3125
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For migrating existing code I have:
with DAO:
i would expect:
User findById(Long id);
but generated is
Optional<User> findById(Long id);
if I duplicate
User findById(Long id);
in UserDAO, it works as expected. Why?
The text was updated successfully, but these errors were encountered: