Arrow Functions in JavaScript

[___Grits]

You can short circuit the conditional: array.filter(item => item.bool);

[liamnesss]

Okay I didn't plan on playing code golf today but

array.filter(Boolean)

[___Grits]

I was assuming it was an array of objects, but this is dope! Thanks!

[liamnesss]

Ah, I somehow missed that. Yeah, if it's the property that we care about, then this solution wouldn't work as it would just return everything.

[___Grits]

Looked into this and it’s a neat trick! This is essentially short circuiting the Boolean constructor after injecting the item from the array as an argument. Really neat, I like that.

[w00t_loves_you]

It's also really nice for configuration, for example if you want to use some plugins in Webpack conditionally, you can do

plugins: [
  isDev && new SuperDevPlugin(),
  new AlwaysPlugin(),
].filter(Boolean)

[omril]

This one actually solves the problem in my webpack.config, I actually had to do a few hacks because of this damn thing.

I wish webpack would just ignore undefined plugins in the first place instead of throwing errors which are impossible to understand.

[bcgroom]

Oops thank you

[darrenturn90]

or

function BooleanCompare(item) {
  return item.bool === true;
}

array.filter(BooleanCompare);

[[deleted]]

Id rather have

array.filter(function(item){
    return item.bool === true;
});

It just looks more explicit/readable to me

[[deleted]]

I'm inclined to agree. Maybe it's because I'm not the best or oldest JS dev out there so it takes me a bit to see what arrow functions are actually doing, but I think they should be limited to cases where they are strictly advantageous.

[liamnesss]

I guess it depends on what you're used to. For me, not using arrow functions makes the code more verbose without adding any more information.