microsoft / microsoft/vscode-edge-devtools
Duplicates command palettes with VS Code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 358
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
I showed the Edge Devtools and js-debug intregration today. Something that came up was the fact that there's two command palettes; if you ctrl+shift+p in the devtools editor, you get a different palette than you do in VS Code.
It would be nice to integrate the commands from the devtools into VS Code command's palette, or at least use quickpicks, for a more consistent experience.
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
Start by comparing the commands shown by Ctrl+Shift+P in the DevTools editor with the VS Code command palette. Check whether the DevTools commands can be integrated into the VS Code palette or exposed through quick picks, and consider the work done when the command experience is consistent between both contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100