Inconsistent TM Scopes for generic class methods when generic argument is on a second line.

[tyler-brandt]

Version: 1.38.0
Commit: 3db7e09f3b61f915d03bbfa58e258d6eee843f35
Date: 2019-09-03T21:47:00.464Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.2.0

( Also tested with Insiders 1.39.0 )

Steps to Reproduce:

1. Write a generic class method in TS
2. Call the generic class method with a type argument spanning multiple lines
3. Observe that the method call is a different color than it would be if it was only on one line

Does this issue occur when all extensions are disabled?: Yes

When it only spans a single line, the method name is given TM scope entity.name.function.ts
When it spans multiple lines, it does not have that scope and the first one listed is variable.other.property.ts

[mjbvz]

Please share the text of the code along with screenshots

[tyler-brandt]

interface foo<T> {
  foo: T;
}

class bar {
  doStuff<T>() {};

  notWorking() {
    this.doStuff<foo<{
      test1: number;
      test2: number;
      test3: number;
      test4: number;
      test5: number;
      test6: number;
      test7: number;
      test8: number;
    }>>();
  }

  workingProperly() {
    this.doStuff<number>();

  }
  alsoWorkingProperly() {
    this.doStuff<foo<{bar: number}>>();

  }
}

[mjbvz]

Possible duplicate of #479

[sheetalkamat]

Duplicate of #475 and limitation of textmate grammar syntax