Flow type arguments at callsites in class bodies

[rattrayalex-stripe]

This flow language feature is broken in class bodies (and possibly elsewhere, I haven't looked):

class Correct extends React.Component<MyProps> {
  myRef = React.createRef();

  render() {
    const {foo} = this.props;
    return null;
  }
}

class NotCorrect extends React.Component<MyProps> {
  myRef = React.createRef<HTMLDivElement>(); // This causes the problem!

  render() {
    const {foo} = this.props;
    return null;
  }
}

[mgtitimoli]

I can confirm it's also broken at function calls on every context (class body and everywhere else).

[gastonmorixe]

+1

[michaelgmcd]

The > character is the issue. When inspecting the TM scope, it seems like it's being treated as the > of an arrow function (meta.function.arrow.js) which seems to break all of the syntax highlighting until the next } (end of the make believe function. This might be a little tricky to debug, but I'll try to take a look when I can.

[michaelgmcd]

Please check that this was fixed in v0.0.24

[rattrayalex-stripe]

Yep, looks perfect!