-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Improve diagnostics when a Bean Override cannot be selected by type #34004
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
Labels
Comments
quaff
added a commit
to quaff/spring-framework
that referenced
this issue
Dec 3, 2024
quaff
added a commit
to quaff/spring-framework
that referenced
this issue
Feb 10, 2025
Close spring-projectsGH-34004 Signed-off-by: Yanming Zhou <[email protected]>
quaff
added a commit
to quaff/spring-framework
that referenced
this issue
Feb 10, 2025
Close spring-projectsGH-34004 Signed-off-by: Yanming Zhou <[email protected]>
sbrannen
pushed a commit
to sbrannen/spring-framework
that referenced
this issue
Feb 10, 2025
See spring-projectsgh-34004 Closes spring-projectsgh-34006 Signed-off-by: Yanming Zhou <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Overview
Whenever a bean override (such as for
@TestBean
,@MockitoBean
, and@MockitoSpyBean
) cannot be selected "by type", we should improve diagnostics for users by pointing out (in the exception's message) that the type selection might have failed because the runtime type of the target bean could not be inferred.Related Issues
@MockitoSpyBean
requires existing bean instance to spy on #33935@MockitoSpyBean
#33965The text was updated successfully, but these errors were encountered: