Test: Use Built-in TypeScript Semantic Highlighting

[aeschli]

Refs: #119139

• macOS @mjbvz
• linux @RMacfarlane
• windows @lszomoru

Complexity: 2

Create Issue

---

• open a typescript file

• verify in the status bar that typescript version 4.2 or newer is used

• open the TS log (Command: TypeScript: Open TS Log...) (might have to do it twice after the restart the TS service)

• In the log, look for the content typescript-vscode-sh-plugin not active for version >= 4.2

• use one of the built in themes (or one that has semantic highlighting enabled (if you know))

• Set a cursor on a variable or other symbols and use the Developer: Inspect Editor Tokens and Scope command to investigate whether semantic tokens are available. If it does, the hover has a section semantic token types

• A easy way to see whether semantic highlighting works is: use default Dark/Light theme and verify that constant variables have a slightly different color than other variables.

• Do some general testing around semantic tokens. E.g. Open large files, scrolling around, validate updating after modifications

• Switch to an other version of TypeScript by opening a folder with package.json depending an typescript < 4.2 and clicking on the version indicator in the status bar

• Check the TS log, low it will say typescript-vscode-sh-plugin initialized. Intercepting getEncodedSemanticClassifications and getEncodedSyntacticClassifications.