Closed bonfiresh closed 4 years ago
Which version of the extension are you running? This was indeed an issue in v1.18.0, but a few hours after its release I fixed this in v1.18.1. Perhaps this is still an issue, but I don't succeed in replicating it anymore.
After looking a bit more into it, it seems that during the whole v1.18.1 release process, the VSIX didn't actually get published to the marketplace. This results in the v1.18.0 with this issue being the last available version.
The original fix happened in deb4de03 (released in v1.18.1: e8ffe0e...1e3921c) and available in v1.18.2 that's now on the marketplace. I've double checked it's properly published this time.
Yes! in the latest v.1.18.2, The problem has been solved. grateful thanks for your work, and this excellent extension!
Hello, on my vscode, the prev version is work fine, but after the current version update, give this err: Thx