Closed BABA983 closed 7 months ago
Breakpoints are only bound once an extension activates. Based on the troubleshooter, it does not appear that the configuration editing extension was activated.
Breakpoints are only bound once an extension activates. Based on the troubleshooter, it does not appear that the configuration editing extension was activated.
It seems the configuration editing extension works when I type some keywords and I get the source map. Not sure which step I got wrong.
The configuration editing extension doesn't activate on editing of settings.json.
This seems to be working as-designed.
Tried to debug a built-in extension named
configuration-editing
in vscode. I tried the following step from the wiki. Just don't work on extension debugging. How can I debug the built-in extension?