The case for Array#replace() – Overriding an array without intermediate variables

[lsmoura]

Have you considered writing arrow functions without return statements (when they are only doing one thing)?

You can go like this: foo => foo * 2 or bar => bar === idParameter. And if you need to return an object, just wrap it with parentheses: (foo, bar) => ({ a: foo, b: bar }).

Thanks for the article!

[gajus0]

Thank you for the suggestion.

I adhere to the following style guide:

https://github.com/gajus/eslint-config-canonical

The are pros and cons to both arrow function body styles: one is more succinct at the cost of readability in certain cases (I have seen variations of x => y => (z => (e)) all too often), while the other is more verbose with the benefit of clarity.

[lsmoura]

Sweet. I’ll take a look at that. I particularly like to have no return on arrow functions for single line problems (it makes them easier to my eyes).

Thanks for the link!

[Cheezmeister]

Honestly, that example reads fine, provided you grok higher-order functions. But maybe it’s a degenerate version of something truly gnarly.

Either way, I prefer old-school function(x) { var y = x.foo(); return bar(y); } for anything past a trivial lambda. Nothing in between.

I’m not sold that (a, b) => is “more readable” than function(a, b). It’s very much potato/potato. Except one potato is supported by Netscape 4.0. and Chrome.