-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverage commands not working anymore since last release #370
Comments
+1. Downgrade to |
vscode-coverage-gutters/tsconfig.json Line 8 in 0247b88
https://www.typescriptlang.org/tsconfig#importHelpers Looks like we need to either turn off |
@ilharp Thanks for the issue. I will take a look at the PR now and we can do another release right away, sorry for the disruption! |
I will do the release in the next hour or so after I confirm the vsix locally. I have a ticket here where I will think on potential fixes and ways to proactively catch these kind of issues in the future. |
Describe the bug
I have launched VSCode this morning and it seems that the extension is not working properly anymore. It doesn't show the watch button in the status bar and when I try to launch it manually it says it doesn't find the command. Here is a screenshot:
From my little experience with VSCode extensions, it might be due to a renaming of the commands in the latest release. Indeed, a new release has been published 14 hours ago, so maybe something has been broken there that passed the tests.
To Reproduce
Steps to reproduce the behaviour:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: