Perform ASI for class properties

[mmazzarolo]

Hello there,
it seems that semicolons are required by Flow for class methods and variables (#825 , #1517) and maybe even in other statements.
Is there any plan for dropping the need of semicolons in the future?
Babel doesn't need them (it has already been discussed in the past) and unfortunately semicolons clash with StandardJS and other common standards/linter configs.

Thank you in advance.

[samwgoldman]

I think an earlier version of the class properties proposal required semicolons, but I believe updated versions allow for automatic semicolon insertion. You still need to be careful about starting a line with ( and [, I imagine.

Kicking this over to Jeff, since he's the authority on this proposal. Thanks, Jeff!

[mmazzarolo]

You still need to be careful about starting a line with ( and [, I imagine.

Yep, you are right, but this is easily forced by linting (and it's not that common).

P.S.: Thanks, the title sounds definitely better now.

[aluanhaddad]

Semicolons are good for your health.

[mmazzarolo]

Hello there!
Should the commit up here have fixed it?
It's still not working for me on flow-bin@0.24.2:

The following snippet works:

/** @flow */
import React, { Component } from 'react'
import { View } from 'react-native'

export default class Test extends Component {

  _testFunction = () => {
    return null
  }; // !!!

  render (): ReactElement {
    return <View />
  }
}

The following snippet returns render (): ReactElement { -> Unexpected identifier

/** @flow */
import React, { Component } from 'react'
import { View } from 'react-native'

export default class Test extends Component {

  _testFunction = () => {
    return null
  }

  render (): ReactElement {
    return <View />
  }
}

Thank you again guys, have a nice day

@marudor

[marudor]

Ah. My Commit was only for Class Properties. Not in general.

[mmazzarolo]

@marudor ouch, thank you anyway
I'd gladly contribute if anyone can point me to the right direction.

[mmazzarolo]

FYI it works fine now on :)
#1517 (comment)