This worked in 0.4.33, broke in 0.4.34, worked again in 0.4.35, and seems to have been broken since 0.4.36. Screenshots below are using 0.4.39.
It affects Typescript test files containing casts. As far as I can see, it prevents parsing of the file, causing codelens run/debug buttons not to be updated.
Example:
Minimal and meaningless test file after a clean restart of VSCode:
Removing the offending line immediately causes the codelens buttons to appear. These work as expected.
Reintroducing the offending line will not cause the codelens buttons to disappear. (But restarting VSCode will).
I suspect, however, that the button locations have just been cached from the last successful parsing of the file. Altering the structure of the file will cause the buttons to render in unexpected places:
This worked in 0.4.33, broke in 0.4.34, worked again in 0.4.35, and seems to have been broken since 0.4.36. Screenshots below are using 0.4.39.
It affects Typescript test files containing casts. As far as I can see, it prevents parsing of the file, causing codelens run/debug buttons not to be updated.
Example:
Minimal and meaningless test file after a clean restart of VSCode:
Removing the offending line immediately causes the codelens buttons to appear. These work as expected.
Reintroducing the offending line will not cause the codelens buttons to disappear. (But restarting VSCode will).
I suspect, however, that the button locations have just been cached from the last successful parsing of the file. Altering the structure of the file will cause the buttons to render in unexpected places: