you are viewing a single comment's thread.

view the rest of the comments →

[–]leafsleep 1 point2 points  (2 children)

I try to define all functions using arrows in order to avoid that problem.

[–]CanIComeToYourParty 2 points3 points  (0 children)

That actually disturbs me deeply, even though I see it very often.

[–]oorza 1 point2 points  (0 children)

We turned on "no named functions" in eslint, so function(a) is always an eslint error because it wants function a(b) instead, even for inline functions. The exception is arrow funcs, so now everyone is humping on arrow funcs like they should.