Missing semicolon doesn't warn for arrow functions in class properties

[pablonete]

Bug Report

• TSLint version: 3.15.1
• TypeScript version: 1.8.10
• Running TSLint via: VSCode

TypeScript code being linted

class A {
    private f = function() { return "f"; }
    private g = () => { return "g"; }
    private h = () => "h"
}

with tslint.json configuration:

"semicolon": [true, "always"],

Actual behavior

Property f gets a warning Missing semicolon.
Properties g and h doesn't.

Expected behavior

Properties g and h should get the same warning.

I can understand that somebody may want to opt-out of this rule, but it seems inconsistent as is.

[jkillian]

This was an intentional change actually, to allow arrow functions to be declared like class methods: #1081

In #1081, we decided that the complexity of adding another option wasn't worth it for this small edge case, sorry!