Arrow Methods incorrectly highlighted as bad code?

[greggman]

Arrow methods are apparently a shipping thing

A normal class

class Foo {
   someMethod() {
   }
}

An arrow class method

class Bar {
   someMethod = () => {
   }
}

this is apparently a shortcut for binding the method to the instance. In other words if I understand correctly it's a shortcut for this

class Bar {
   constructor() {
      this.someMethod = this.someMethod.bind(this);
   }
   someMethod{
   }
}

It's already working in Chrome but JSFiddle is marking it as bad code

Note: It doesn't work in Firefox Nightly nor Safari Tech Preview so maybe I'm jumping the gun here.

[oskarkrawczyk]

I can't seem to find a ECMA proposal for this, nor a list of browsers that plan to support it.

@greggman Any chance you have it somewhere?

Worth asking if @jshint will be willing to add it to the linter.

[greggman]

It falls out of this proposal

https://github.com/tc39/proposal-class-fields

In particular this section

https://github.com/tc39/proposal-class-fields#execution-of-initializer-expressions

says points out they're basically field declarations and they're evaluated anytime the class is constructed/intialized

They've been shipping since Chrome 72

https://developers.google.com/web/updates/2019/01/nic72#public-class-fields

[greggman]

Note that private class fields also shipped

https://developers.google.com/web/updates/2019/04/nic74#private-class-fields

[greggman]

browsers: Chrome, Opera, Edge(Chromium Version), Firefox, Safari

[oskarkrawczyk]

Note to self:

Update JSHint if this ticket is closed: jshint/jshint#3139

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.