eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
Do not show DAP tracing while debugging, at least not by default
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
This issue is split from #1424.
Apart from plugin developers, there's little interest for the DAP output console. It obscures the actual process console and users can be fooled easily into thinking that the process output is misteriously hidden, while it's actually available into another console within the Console view.
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
The issue names no files, tests, or entry points. Start by locating the DAP tracing output console and the logic that makes it visible during debugging; done means the DAP console is hidden by default while remaining available in the Console view for plugin developers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100