While testing microsoft/vscode#105881 I noticed a case:

1. Change a file (but do not stage it)
2. Run Git: Commit Empty
3. Say that you're sure you want to create an empty commit
4. You're presented with this screen. There's no way to get past it and create an empty commit without stashing/discarding local changes 🐛

![](https://memes.peet.io/img/20-09-8768b030

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: macOS
• Vetur version: 0.27.1
• VS Code version: 1.48.2

Problem

When a component get missing props warning, it highlights a

Most of the time when I'm using this extension I am using it to mark points of interest during research. A task that I've had to perform lately is looking for hard coded text in various applications that needs to be moved to our CMS. This extension works great for that with one exception:

Generally after I have performed my research I need to document it. Using this extension I need to go to ea

Setting peacock.color or peacock.remoteColor in the user settings.json can be done manually. If set, peacock will use that color as the default color to colorize VS Code.

This should be documented in the readme, along with considerations.

Considerations:

• this can only be set or unset manually.
• this will make every vs code instance that doesnt have a color in their workspace use t