-
Notifications
You must be signed in to change notification settings - Fork 211
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
Symbols view should nest elements by their surrounding scope #1431
Labels
for: eclipse
something that is specific for Eclipse
for: vscode
something that is specific for VSCode
theme: spring index & symbols
theme: structural view
type: enhancement
Milestone
Comments
martinlippert
added a commit
that referenced
this issue
Jan 15, 2025
There is bit of groundwork necessary to fully materialize this on the UI side, but the groundwork is already underway. I hope for the hierarchical view of symbols to appear in the outline view of VSCode as the first step (probably for the |
martinlippert
added a commit
that referenced
this issue
Feb 20, 2025
martinlippert
added a commit
that referenced
this issue
Feb 20, 2025
martinlippert
added a commit
that referenced
this issue
Feb 20, 2025
martinlippert
added a commit
that referenced
this issue
Feb 20, 2025
martinlippert
added a commit
that referenced
this issue
Feb 20, 2025
martinlippert
added a commit
that referenced
this issue
Feb 20, 2025
martinlippert
added a commit
that referenced
this issue
Feb 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
for: eclipse
something that is specific for Eclipse
for: vscode
something that is specific for VSCode
theme: spring index & symbols
theme: structural view
type: enhancement
For a Spring MVC controller class like this:
the Spring Symbols view creates multiple top-level entries:
/path
It would be nice if the elements were nested inside each other. The parameter annotation as a nested node underneath the method, that in turn underneath the bean etc. Otherwise (and currently) you might end up with a gazillion of
@RequestParam
list entries that – without that contextual information – are not really helpful on their own.The text was updated successfully, but these errors were encountered: