microsoft / microsoft/vscode-edge-devtools
bug in the output of the VSCODE
Open
Nobody has claimed this yet.
bug
tracked
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 358
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
Describe the solution you'd like:
Describe alternatives you've considered:
Additional context:
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 provides no reproduction steps, expected output, actual output, affected VS Code entry point, or test location. Start by requesting or reproducing the reported output in the vscode-edge-devtools extension; the work is not ready to start until the incorrect behavior and a verifiable expected result are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100