spring-projects / spring-projects/spring-tools
[vscode-spring-boot] Add visual clues and code action entry points when detecting Spring classes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
Currently, when a user works on a Spring component, VS Code does not show anything special. However, in both Eclipse and STS, we can see that IDEs display a green icon next to the Spring class. This provides a very strong clue to the user as the IDE is recognizing the Spring component. I think this would be a very useful visual clue and can lead to a lot of visibility of our Spring improvements
Currently based on the support of VS Code UX APIs (and after discussing with VS Code folks), this will be most likely be in the form of GitLen style (line blames), we will experiment with it first and see how it looks first, then decide if we want to make it into the final release.
(cc: @martinlippert @Eskibear)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing Spring component detection and the VS Code UX APIs, using the proposed GitLen-style presentation as the experiment scope; done is not defined because the issue leaves the final visual treatment and release decision open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100