Join egghead, unlock knowledge.

Want more egghead? It's 45% off for a limited time only!

This lesson is for members. Join us? Get access to all 3,000+ tutorials + a community with expert developers around the world.

Unlock All Content for 45% Off

Already subscribed? Sign In

Save 45% for a limited time.

Get access to all courses and lessons on egghead today.

Autoplay

    Advanced React Component Patterns Update

    Improve debuggability of Higher Order Components

    Kent C. DoddsKent C. Dodds

    React DevTools and React's built-in development warnings rely on the displayName and name property of your react components to give you a good developer experience. Unfortunately, Higher Order Components make it harder for React to give that good experience. In this lesson, we’ll learn about the displayName property and how that impacts React Developer Tools. Then we'll improve the displayName for our Higher Order Component by changing where we call the withToggle Higher Order Component.

    reactReact
    Code

    Code

    Become a Member to view code

    You must be a Member to view code

    Access all courses and lessons, track your progress, gain confidence and expertise.

    Become a Member
    and unlock code for this lesson
    Transcript

    Transcript

    00:00 The React dev tool is a really handy tool to allow us to interact with our live React application. For example, if I wanted to interact with the toggle component, I just simply search for it there and then I can toggle the onState of the toggle component and it updates my app in real time, which is pretty cool.

    00:15 Now let's say I wanted to interact with the myToggle component. I'll just search for that and I get no search results. Why is that? What's going on here? The way that React works with the component tree here is it's going to take the name of the component and in this case, this component is a function. The name property of app is going to be app.

    00:35 Now, if we didn't like that we could actually change it by adding a displayName prop. We said appDisplayName=myApp. We save that and we're going to get myApp instead. That's handy. It'll use the name prop by default and if we want to override it we can use displayName. But I like the default so we'll just get rid of that.

    00:54 Next, if we jump into the app component we're going to see toggle. Toggle is a class. If we scroll up to the toggle class we'll see the class name for the toggle class is toggle and that's why we're seeing toggle there.

    01:06 Then if we go a level deeper we're going to see a div with a whole bunch of wrappers. Why is that? This is because we're using withToggle for all the components that we're rendering as children of the toggle component. withToggle creates a new component called wrapper, and the name property of wrapper is going to be wrapper.

    01:25 If I go in here -- this is where the myToggle component lives -- we get unknown. That's because the component that's being rendered here actually doesn't have a name property. There's no way to infer the name from this anonymous arrow function. It simply puts unknown.

    01:43 One thing that we could do to improve this a little bit is by just pulling this out and making a new component called constMyToggle and that's the actual toggle component that's rendering things. Then we put it inside this withToggle call and then we'll call this myToggleWrapper and then down here we'll render myToggleWrapper.

    02:04 Now if we expand these all the way down to this wrapper, we're going to get myToggle there. What's going on here is this arrow function is getting an inferred name property and so myToggle.name is going to be myToggle.

    02:16 But this wrapper is still not all that useful. It could be a wrapper for anything. What if I have another higher-order component that uses the function name wrapper? What I could do here is I could say wrapper.displayName=withToggle. Then I can open up the app, toggle, and see I have all of these withToggle components.

    02:37 We could make it even more useful by putting the component's name right inside of there. Let's make this a template string. We'll say component.displayName. We save that. We go app, toggle, and we're going to get undefined for a lot of these. That's because in this case it's actually the name property, not the display name. One thing we could do is just say myToggle.displayName=myToggle. That would solve it for this case, myToggle right there. Perfect.

    03:11 Or we could just say we're going to use the display name or the name. Now if we open up app and toggle, then we're going to get a couple that don't actually have a name. But we'll also get this one that does. The reason that these ones don't have a name is that these are inline arrow functions. They're totally anonymous, which is unfortunate. That's just one of the problems of higher-order components, is that the display name can be a little bit tricky.

    03:37 Some popular libraries will expose a Babel plugin that will automatically add a display name prop to this so that it can have something more useful for you. But it's definitely a challenge to give a good display name for everything. One thing that we could do is we'll just extract this just like we did below. Then this is going to be a little bit nicer, but then we have to reassign this and use that one instead. It can be a little bit of a pain.

    04:07 What we're going to do, we're going to remove the withToggle wrapping around all of these. Then we'll add the withToggle wrapping here. Now if we look at the display name it's going to be a lot more helpful.

    04:23 In review, if you want to have a good display name for your higher-order components, then you need to monkey-patch a display name property right on the wrapper, so that it overrides the default name property from the wrapper and gives React dev tools and warnings in the React console to have something that's a little bit more useful.

    Discuss

    Discuss