-
Notifications
You must be signed in to change notification settings - Fork 210
Navigational aid for Spring Events #1348
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Thanks @jonsmithers for raising this enhancement request, sounds indeed like a great feature to add. Let's see how we can get this realized. Do you use the Spring Tools in Eclipse or VSCode? |
Using vscode here! And awesome, thank you! |
Moving out to |
The first version of this includes basic information about event listeners and event publishers in the internal index for Spring elements and allows to use the "Go To References" feature inside of VSCode to find all publishers for the specific event type when invoked from a listener and vice versa. There are no gutter icons or features in the gutter for this specifically, the type hierarchy of events is not yet taken into account, and there is no way to invoke this from the Java editor inside of Eclipse yet. All those things should be captured in separate issues as improvements moving forward. |
(please note that even though the |
Expected Behavior
Anytime you trigger or listen for a spring event, IntelliJ presents these gutter icons. When clicked, a popup will list every place that triggers the event you're listening for OR every place that listens for the event that you're triggering, allowing you to easily jump to these locations. I like this feature.
Current Behavior
Currently there is nothing to aid navigation between event listeners and triggerers.
Context
This feature is pretty handy in a codebase that relies on Spring Events.
As an alternative, I could consider refactoring the code to not use Spring Events. Spring Events are harder to navigate compared to plain old function invocations, unless the IDE provides this navigational aid.
The text was updated successfully, but these errors were encountered: