Ben Ilegbodu 🏀👨🏾‍💻 Profile picture
Jul 22, 2021 13 tweets 5 min read Read on X
The .reduce() method is maybe the most powerful, yet least understood array method. It basically allows us to transform an array into... nearly anything else

Let's re-implement 1️⃣0️⃣ lodash functions to learn more about how for examples on how .reduce works

/thread 👇🏾🧵
1️⃣ sum()

ℹ️ Computes the sum of the values in an array

The function is called a "reducer" & the 2nd param is our initial value

The 1st arg of the reducer is the "accumulator" (the value we're building up). The 2nd is the current array element in the iteration

/thread 👇🏾🧵
2️⃣ countBy()

ℹ️ Creates an object w/ keys that are the array elements and values that are their counts

Here we're turning an array into an object

(can't forget to return the object we're accumulating!)

/thread 👇🏾🧵
3️⃣ flatten()

ℹ️ Flattens the array a single level deep (also available as .flat() since ES2019)

Here we go from an array to a new (& flattened) array. A "flatDeep()" would need to be recursive

/thread 👇🏾🧵
4️⃣ filter()

ℹ️ Iterates over the array, returning a new one containing the elements that pass the test implemented in the "predicate" function

Of course .filter() already exists on arrays, but this shows how it can implement one of the *main* array utility methods

/thread 👇🏾🧵
5️⃣ fromPairs()

ℹ️ Returns an object composed from key-value tuple pairs (equivalent to `Object.fromEntries()`added in ES2019)

/thread 👇🏾🧵
6️⃣ keyBy()

ℹ️ Creates an object lookup using the property name as the lookup key

/thread 👇🏾🧵
7️⃣ map()

ℹ️ Creates a new array of values populated w/ the result of calling the mapper function on every element in the array (already exists of course as .map())

Shout out to the exponentiation (**) operator (ES2016) which is shortcut syntax for `Math.pow`

/thread 👇🏾🧵
8️⃣ max()

ℹ️ Computes the maximum value w/in the array

(FYI - we can actually use the spread operator w/ `Math.max` to implement this with far less code 🤯)

/thread 👇🏾🧵
9️⃣ some()

ℹ️ Tests whether at least one element in the array passes the test implemented by the "predicate" function (exists as .some() on arrays)

This shows reducing an array to a boolean. But is sub-optimal because it doesn't short-circuit like .some() does

/thread 👇🏾🧵
1️⃣0️⃣ zip()

ℹ️ Creates an array of grouped elements by index

Here we get to use the 3rd arg of the reduce function, which is the value's index w/in the array

/thread 👇🏾🧵
How do you feel about .reduce()? It took me a while, but once I got the hang of it, it leveled up my JS data transformation skills

Feel free to check out my latest post on re-implementing lodash functions w/ .reduce() for more info

/thread 👇🏾🧵

benmvp.com/blog/learn-arr…
If you love JavaScript like I do and wanna learn more about it (like I do), you should subscribe to the BenMVP Newsletter. Every week I share something new about JS, TS, React, DivOps, or all of them combined!

Keep learning my friends. 🤓

benmvp.com/subscribe/?utm…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Ben Ilegbodu 🏀👨🏾‍💻

Ben Ilegbodu 🏀👨🏾‍💻 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @benmvp

Dec 23, 2021
I recently created a TypeScript generic utility type that recursively converted `Date` types into Firestore `Timestamp` types

The type was fun to come up w/ cuz I learned a lot but it's also a bit complex. Lemme break down all the TS features line by line...

/thread 🧵👇🏾
`ToFirestore<>` takes a single generic type param, `MaybeDate`. If it is a `Date` type, then the "true" branch of the type conditional returns a `Timestamp` type instead. This base case of the recursive type serves as the crux of the mapping of `Date` ➡️ `Timestamp` type

🧵👇🏾
The "false" branch of the outer conditional begins a nested one that converts `Date` ➡️ `Timestamp` types of an array type by recursively calling `ToFirestore<>` on the array item type

(the `infer` keyword auto-creates a new generic type that's the array items type)

🧵👇🏾
Read 8 tweets
Nov 18, 2021
Something that always comes up when I teach React + TypeScript is "interfaces vs type aliases" for props & other object type definitions

95%+* of the time they're interchangeable. But let's look at practical cases where we might favor one over the other 👀

/thread 🧵👇🏾
First the similarities. Both interfaces & type aliases can...

✅ Define an object type (duh!)
✅ Merge/extend either interfaces or type aliases
✅ Use generic types

🧵👇🏾
We need type aliases for...

➡️ Defining discriminated unions
➡️ Extending discriminated unions
➡️ Using built-in utilities or other custom generic types

(technically interfaces can extend utility types but it's ugly IMO 🤮)

🧵👇🏾
Read 7 tweets
Oct 28, 2021
TypeScript's type system is very powerful because it allows us to express types in terms of other types, including generics

I was looking at the implementation of the TS utilities & learned lots about how to implement generics, so I wanted to share my learnings

/thread 🧵👇🏾
1️⃣ Basic generics

Generic types are like implicit return funcs. They take 1+ params & return a new type

`Partial<>`, `Required<>` & `Readonly<>` take any obj type & return a new obj type w/ property modifiers

We can use them as an example for our own `Mutable<>` util!

🧵👇🏾
2️⃣ Generic constraints

Using `extends` we can restrict what types of params are allowed. It's kinda like providing types of our generic params

`Record<>` limits the `Keys` param to only `string`, `number` or `symbol` cuz JS objects only allow those types as keys

🧵👇🏾
Read 9 tweets
Oct 13, 2021
What are some situations for when we can use the `useCallback()` & `useMemo()` Hooks in React components?

Well, one case where we need `useCallback()` is when we call a helper function w/in `useEffect()`, so we need "referential equality" to include it in deps

/thread 🧵👇🏾
I also use `useCallback()` by default when returning a function from a custom Hook cuz I dunno how that function will be used w/in host components

`useCallback()` gives a stable function reference similar to the updater func from `useState()` (the 2nd array element)

🧵👇🏾
The `useMemo()` Hook is similar to `useCallback()` except that it memoizes any value not just functions

So I use `useMemo()` in the same situations: when I have a derived object/array that's used in the deps of `useEffect()`

(I like to think of "memoization" as a cache)

🧵👇🏾
Read 8 tweets
Jun 1, 2021
React component patterns help us create reusable and extendable components that provide some inversion of control to their parent

Here's a thread of 5️⃣ such patterns

But first let's start with a vanilla <Button> component with "normal" props & how it's used

/thread 🧵👇🏾 ImageImage
1️⃣ Placeholder props

The placeholder props pattern allows the shared component to control its layout & any logic, but give some control to the parent for the display

For our Button comp, the `startIcon` & `endIcon` props can be <svg>, <img> or even other React components

🧵👇🏾 ImageImage
2️⃣ Polymorphic components

The polymorphic component pattern comes in handy when we need flexibility on the rendered element

For semantic HTML or a11y reasons we may need to change the root element. We can even pass another component for the `as` prop (react-router <Link>)

🧵👇🏾 ImageImageImage
Read 8 tweets
May 19, 2021
Nope JSX doesn't have a built-in loop construct. Instead it offloads looping to JavaScript & just accepts an array of JSX elements for rendering lists

💡 So in React, to loop we gotta convert an array of data ➡️ array of JSX elements

Let's look at some ways how...

/thread 🧵👇🏾
Calling `.map` on the array is the most popular way to generate that array of JSX elements

And cuz `.map` returns a new array we can inline it directly in the JSX w/o using a var (also very common)

Putting the `.map` inline makes it *feel* like traditional loop templates

🧵👇🏾
Using a regular `for` loop (or `for-of`, `.forEach`, etc) requires a var that we gotta `.push` into

`for` is likely more familiar to JS newcomers but it means we cannot inline the code

...unless we wanna go rogue and put it in an IIFE 🤯 (anyone used one here before???)

🧵👇🏾
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(