Building a simple and reusable modal with React hooks and portalsby Theo Salzmann on 11.10.2019
A lot of interesting new things have been added to React in the last two years. For me personally hooks have probably been the most exciting addition in recent years. Before hooks I pretty much always used recompose , a simple helper library consisting of some higher-order components to wrap functional components with state or lifecycle access.
Now that we have hooks, it is easier than ever to add state or side effects to a functional react component. To highlight this I will show you how you can build a simple general purpose useModal() hook. We will also make sure that our modal will always be rendered into a specific DOM node. So no matter where we use the modal inside our react component tree, it will be a direct descendant of a predefined div.
Without further ado let's dive right in:
To build a small react app we first need our basic skeleton. I assume that you are familiar with the basics of react and have some understanding of how a very basic react app is structured. So I skip the standard index.html file here, as we won't do anything out of the ordinary with it.
So our basic skeleton is just a plain index.tsx file consisting of our ReactDOM.render() call with our main <App/> component. We will soon have a closer look at this component, but first I would like to create our actual <Modal />.
Below you see the code we use for our very simple modal. We won't style our modal or do other fancy stuff during this tutorial, as its main purpose is to showcase some implementation details.
So let's have a look at the API of our modal. We expect a closeModal() callback function which will be triggered whenever our close button is pressed. Apart from that we just render any children passed to our modal inside our div.
You might already have guessed what the whole ReactDOM.createPortal() thing around our div is. Like ReactDOM.render() createPortal() allows us to define a specific DOM-element where our component will always be rendered to. In this case our DOM element should exist and have the id attribute "modal-root". We will soon define this element inside our main <App/> component, so bear with me :) .
Note: The wrapping call to React.memo() is an optimization which is fairly similar to extending React.PureComponent in good old class components.
Defining our custom useModal hook
While we have already created a re-usable component which will actually render to a specific DOM node, we haven't built the actual modal functionality yet. To open and close our modal we do need some form of state. Let's model our state as an isVisible boolean.
To do this we import the useState() hook from React and call it inside our functional component with a default value of false. useState() returns an array which holds the current state value at index 0 and a function to transform the state at index 1. Thanks to ES6s beautiful destructuring syntax, we can simply destructure both values into their own respective variable (see line 12 below). We also define two convenience methods show() and hide() to make our state transformations even more explicit and readable.
The last part of our custom hook is our <RenderModal/> component. This component hands any children we pass to it to the <Modal/> component we defined earlier. It will also only render them, if our modal is actually visible. Because we created an enclosing scope around our render modal, we also have access to our hide() function, which we pass to the closeModal-prop of our <Modal/>-Component.
Last but not least, we return
- an object from our hook, containing the show() function, which has to be called outside of our modal,
- the hide() function (in case we want to add additional triggers to close the modal) and
- our <RenderModal/>-component.
We could also have exported our hook elements inside an array, like useState() does, but having actual named properties gives us a bit more flexibility when consuming our hook. You will soon see what this looks like.
Using the hook
Now that we have everything in place, we can build our actual app. Our <App/> consists of two main parts:
1. A <div> containing a button to open our <Modal/>, and our <RenderModal/> component
2. Another <div> which has our 'modal-root'-id. This is where all our modals will actually be rendered to.
In line 6 we use our custom useModal() hook. Note that we just destructure show() and <RenderModal/> by using the object destructuring syntax. Here it comes in handy, that our hook returns an object instead of an array, as it allows us to easily specify which parts of our hooks we actually need, by naming them.
Our show() function is now passed to the onClick() handler prop of our <button/>. Our <RenderModal> component on the other hand can be used like any other React component. In our example we pass a <p>-tag with some text as children to it.
Rendering multiple modals
We can even render multiple modals this way. Because we abstracted our whole component state away into a re-usable hook, we can just call it twice to create our respective components and and handler functions (see line 6 and 7).
Wrapping it up
We created a simple and re-usable modal solution with react hooks and portals. This component can be easily enhanced. We could, for example, make our <Modal/>-component more complex to use a title- and a body-prop instead of just passing it children. This way we could have a predefined layout, which would be used by every modal. We could also export the isVisible-state from our useModal() hook and use it inside our surrounding application (e.g. to show an additional hint only when the modal is visible).
I hope you are as inspired by hooks as I am. Thanks for reading and happy coding =)