TS syntax highlighting messed up in VS2022 after update to 17.5.x

[jbertagnolli]

Bug Report

After taking the VS2022 update 17.5.0 on 2/28/2023, syntax highlighting in Typescript became wonky. The issue is still present after taking the 17.5.1 update today (3/1/2023). My coworker who didn't take the 17.5.1 update was able to rollback to 17.4.x to confirm that everything works fine there.

Steps to reproduce:

1. Create an empty *.ts file
2. Open the file in Visual Studio 2022 v17.5.0+
3. Copy the code below into the contents of your new .ts file

export class MyClass {
    public myProperty: any;

    constructor() {
        let myVar = <string>this.myProperty;

        //some comments
        //some more comments
        //ya ya

        for (let i = 0; i < 100; i++) {
            console.log(i.toString());
        }
    }
}

Notice incorrect syntax highlighting here:

But if I change let myVar = <string>this.myProperty; to let myVar = this.myProperty;, the issue goes away:

🔎 Search Terms

visual studio, 17.5.0, 17.5.1, typescript syntax highlighting

🕗 Version & Regression Information

Issue exists in Visual Studio versions 17.5.0 and 17.5.1 but not 17.4.4.

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: typescript@next
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

^I just tried this with the same issue.

• This changed between versions 17.4.4 and 17.5.0

[joj]

This is a known issue for which I believe we have a fix. Assigning to @armanio123 to confirm and provide more detail.

[armanio123]

It has been fixed and is going to be available on Visual Studio version 17.6.2.

[jbertagnolli]

Thanks so much!

[Metritutus]

It has been fixed and is going to be available on Visual Studio version 17.6.2.

Are you able to confirm if this was a typo and meant to be 17.5.2, or if the fix for this issue really is many versions away?

I ask only because, having updated to version 17.5.2, the issue appears to still remain. From what I can tell, it seems to relate to the use of angle-bracket type assertion syntax.

The following code demonstrates the behaviour:

export function someFunction() {
    let test: unknown = 47;
    let test2: number = <number>test;
    let test3: number = test2;
}

Screenshot: