-
Notifications
You must be signed in to change notification settings - Fork 208
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
vscode @DependsOn navigation not linked #1254
Comments
@martinlippert , thank you for looking into this. |
Actually, the case with an upper case - Will add proper support for navigating to the actual referenced bean definition. Just keep in mind that there might be multiple definitions for that bean being found in your project. |
@lamplification Thanks again for reporting this and for proving a demo project. Much appreciated. |
@martinlippert , thank you for the quick turn around! |
In VSCode, you could switch the extension install over to the pre-release to try this out already, btw. |
@martinlippert , I switched to pre-release and that patch works like a charm! Thank you! |
Awesome, great to hear it works for you. Thanks for the feedback! |
Spring uses the class name and converts the first letter to lowercase by default. In vscode, @dependsOn("BEAN_NAME") won't able to find the bean and not able to navigate to DependsOn bean class.
To Reproduce
Create 2 Compoments.
Notice DependsOn(
testBean1
) is not clickable.If it use the class name TestBean1 then that will work, but it won't work during the run time.
demo.tar.gz
The text was updated successfully, but these errors were encountered: