eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
All program launches imply debugging in Eclipse 4.30
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
I'm running the latest Wild Web Developer 1.3.3.202311211923 on Eclipse 4.30, which I've just upgraded. Following this switch from Eclipse 4.29 to 4.30 I had the unpleasant surprise too see that running a JS file is identical to debugging it. There's no difference between choosing "Run As" -> "Node program" and "Debug As" -> "Node program":
Combined with the fact that the debugging itself clears the program's output from the Console view and seemingly replaces it with debug tracing like
Debug server listening at ::1:35157
{
seq: 11,
type: 'response',
request_seq: 6,
command: 'threads',
success: true,
body: { threads: [ [Object] ] }
}
it's really annoying. There are actually two consoles, the one with the program's output is hidded by another containing the debug adapter output.
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
Reproduce the issue in Wild Web Developer 1.3.3 on Eclipse 4.30 by comparing Run As → Node program with Debug As → Node program. Investigate the Node launch and Console behavior; done means running does not imply debugging, and the program output remains visible instead of being replaced by debug adapter tracing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100