TIL you can just do .filter(Boolean) instead of .filter((prop) => !!prop)

founder of eventcaster (@event / events.xyz), hosting /latenightcrew, member of 🍊 dao

building products in web3, hacking /farhack, yapping /dylan | dylansteck.com

i haven't used this syntax before but saw it in a repo the other week and was surprised it exists -- much cleaner IMO

something sweet about passing functions direct to filter, even others like:

users.filter(isPremium)
posts.map(hydrateCast)

building /automod, /glass • prev manifold.xyz, twilio.com

yeah that syntax is so clean! for whatever reason I just hadn't discovered Boolean() until this point

I need to add custom chat gpt instructions to always generate that way

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

Chiang Mai, Mueang Chiang Mai District, Chiang Mai, Thailand

It’s obsolete as of yesterday’s TypeScript candidate release, but I had an `isTruthy` helper function wrapping `Boolean()` that included proper type narrowing too.

Oh that's kinda cute, it's like an Object construction form of a type cast

History tid-bit: APL from the 1960's started using arrays made of 0 and 1 as a "view array". When you overlay an array with a view array on top of each other, the resulting array only has elements where the view array has an element 1 at a given index. This is denoted simply as /. So, 0 1 1 0 / 1 2 3 4 outputs 2 3.