Feature request: Improve output console color scheme
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, spring-boot, typescript, vscode
- Domain
- developer-experience, tooling
Research direction
Start by tracing how the Java extension handles Spring Boot launch configurations and how arguments from launch.json are assembled; compare the application.properties and launch.json approaches described here. Define the settings.json on/off behavior, then verify that a Spring Boot project receives ANSI output by default and that the option can disable it.
Written by the indexing model from the issue text.
Description
For Spring Boot projects, the debug output console should have a nice coloring theme by default, which is not the case currently.
With default settings, all text is a single color which is not very readable.
There is a related StackOverflow question regarding this: https://stackoverflow.com/questions/62280290/provide-color-theme-to-the-java-process-console-in-the-terminal-of-vscode-whil
Currently, there are two (easy, but not scalable) ways how to achieve the desired coloring:
- Add
spring.output.ansi.enabled=ALWAYStoapplication.propertiesfile -> The issue with this approach is that it has to be set up for each project and it just adds unnecessary complexity to application.properties. - Add
"args": "--spring.output.ansi.enabled=ALWAYS"in launch.json -> This issue with this approach is that it also needs to be set up per-project basis and it is not so easy to share configuration as .vscode directory is not within version control scope.
Proposed Solution
I suggest a solution that VS Code pass "args": "--spring.output.ansi.enabled=ALWAYS" by default for Spring Boot projects. There should be an option to control it (on/off) maybe within settings.json
Before

After

@nickzhums Please review.
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/vscode-java-pack
-
Memory Leak in Linux Openai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/vscode-java-pack#1543 · 8 comments · 4 reactions ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-java-pack#1443 · 1 comment · 2 reactions ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/vscode-java-pack#1425 · 1 comment ·
-
ai-triaged enhancement feature-request
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/vscode-java-pack#1423 · 2 comments · 1 reaction ·
-
ai-triaged area/jdtls bug needs-investigation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/vscode-java-pack#1420 · 1 comment ·
All issues in microsoft/vscode-java-pack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·