Name: Explaining the useListener Code
Uploaded: 2020-08-10T17:27:00-05:00
Description: We went through creating custom React hooks to support our callback and closure patterns pretty quickly. Let's take a second to review how everything fits together before we move on.

Adding React to a Vanilla Parcel Project

Create a Broadcaster in React with useState and useEffect Hooks

Create a Custom useBroadcaster Hook

Pass a Listener to a useCallback Hook

Create a Custom useListener Hook Around useCallback

Explaining the useListener Code

Map a Sequence of Values in React with useBroadcaster

Handling an Enter Keypress with useListener and React

Map a Sequence Based on Input Text in React

Creating a Debounce Operator to Limit Listener Calls

Wrap Fetch in a Broadcaster in React

Cancel a Fetch Request with a Broadcaster and React

Map an Error to a Broadcaster Value in React

Bringing the Pattern into React

We went through creating custom React hooks to support our callback and closure patterns pretty quickly. Let's take a second to review how everything fits together before we move on.

https://app.egghead.io/api/v1/lessons/react-explaining-the-uselistener-code/subtitles

Instructor: [0:00] I want to be clear on how useListener and useBroadcaster work together. If we look at useListener and its internal callback listener, this might look more familiar if this was renamed to broadcaster and then this was renamed to listener.

[0:19] When used in this way, this callback can act as a broadcaster that receives a listener of setState. The first time this function is called is this exact line where setState is passed into or up to this function. This setState, which originates from here, arrives here and is assigned to our listener.

[0:47] In the future, we'll undo those, this block is ignored and the listener itself is simply a call to setState. This might make more sense if you looked at this as setState because on that first pass, when this is invoked with setState, then it's assigned, but in subsequent passes, the values come through, and we just pass those values to setState.

[1:16] The goal of useListener was to write a callback that could be fired by these events, then also use it as a broadcaster, and allow us to use our operators on that callback. The solution here, which is a bit clever, which I try to avoid...

[1:35] Since on this first pass, this function is a broadcaster, and on the second pass, it's a listener. On the first pass, this is a listener. On the second pass, that value is going into the listener defined. That's the solution I came up with so that useListener and useBroadcaster could work together inside of the React model.

Explaining the useListener Code

Share this video with your friends

Course

Bringing the Pattern into React