The extensions is always asking for a Restart when having a workspace customization
See original GitHub issueVSCode: 1.13.1 & 1.14.0-insider
Since 7.10.0 has been published it seems that we introduced some kind of bug and the extension is always asking me for a restart when I’m working in my Angular project.
This doesn’t happen in any other kind of projects.
I think the project detection system is messing with the manual change detection
in the settings.
For the moment, I have to completely disable the new feature 😢
It’s strange because I never observed this behavior when developing or testing.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
How to reset VSCode extensions for a workspace
Enable all extensions for workspace · Open a new VSCode window · Goto extensions and filter by @disabled. You can also do @enabled...
Read more >Managing Extensions in Visual Studio Code
Discover, add, update, disable and uninstall Visual Studio Code extensions (plug-ins) through the Extension Marketplace.
Read more >I removed your extension from my browser, but it keeps ...
We have not done anything to cause our extension to reappear after it's removed. ... 1) Go to your online Google Account to...
Read more >Get extensions to customize Safari on iPad - Apple Support
In Safari on iPad, install extensions to customize the way your browser works. ... Important: Check which extensions you have installed and make...
Read more >How to quickly fix common recording errors - Loom support
Here's a quick checklist we suggest you run through if you're having issues. ... Loom Chrome extension Desktop appiOS AppAndroid App. Restart your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK then. The debugging of the issue is all yours. 😄
Fixed it in latest PR. Already published.