Closed bsmith-cycorp closed 5 years ago
Ran into this as well.
Update: reverting to VSCode v1.30 did not fix this, but reverting this extension to v0.0.21 did.
Yep, it looks like this was a regression in 0.0.22. I'll look into this when I can. Some of the work in 0.0.22 is required for #33.
Fortunately VSCode now has a very easy way to revert an extension: find the extension in the extensions view, right-click it, and click "Install Another Version..."
This issue is fixed in the latest release.
This seems to be new as-of VSCode 1.31; we've had cases like this in our code for months and I only noticed the problem today. The problem doesn't happen after removing the
??
(and the following value).