Cover image for The neatest way to handle alert dialogs in React 🥰

The neatest way to handle alert dialogs in React 🥰

dmtrkovalenko profile image Dmitriy Kovalenko ・3 min read

Time to read — 5 mins ☕️

Hola! Lazy dev here and we will talk about handling dialog alerts in react without tears 😢. If you are tired of tons of copy-pastes just to create new freaking «one question» modal dialog — prepare your coffee we are starting.

The goal

We want to make the neatest solution for displaying an alert. Pretty similar to what we have in a browser with a native alert function.

const isConfirmed = alert("Are you sure you want to remove this burrito?");

if (isConfirmed) {
  await api.deleteThisAwfulBurrito();

Sneak peek

Finally we will get to something like this.

const YourAwesomeComponent = () => {
  const confirm = useConfirmation()

    variant: "danger",
    title: "Are you sure you want to remove this burrito?",
    description: "If you will remove this burrito you will regret it 😡!!"
  }).then(() => {

Interested? Let's write some code.

First of all, we need to start with creating actually the modal dialog. This is just a simple alert dialog built with ❤️ and material-ui

import {
} from "@material-ui/core";

export const ConfirmationDialog = ({
}) => {
  return (
    <Dialog open={open}>
        <Button color="primary" onClick={onSubmit}>
          YES, I AGREE
        <Button color="primary" onClick={onClose} autoFocus>

OK, but how we will adopt it to be working dynamically? That's an interesting thing to consider. Why do we need a lot of dialogs for each component if the user can see only one alert dialog simultaneously?

If you are showing an alert dialog over the other alert dialog...you probably need to reconsider the UX part of your application.
No god please no image

So here we go. Everything we need is to render only 1 top-level modal at the root of our application and show it when we need to. We'll use the power of react hooks to make it looks gracefully.

Wrap the context

Let's create a new context instance and wrap our component tree with it. Also, create a simple state that will save the currently displaying options for the alert (like title, description and everything you need).

interface ConfirmationOptions {
  title: string;
  description: string;

const ConfirmationServiceContext = React.createContext<
  // we will pass the openning dialog function directly to consumers
  (options: ConfirmationOptions) => Promise<void>

export const ConfirmationServiceProvider= ({ children }) => {
  const [
  ] = React.useState<ConfirmationOptions | null>(null);

  const openConfirmation = (options: ConfirmationOptions) => {
    return Promise.resolve()

  return (

      <Dialog open={Boolean(confirmationState)} {...confirmationState} />

Now our dialog will be opened once we connect any consumer and call the provided function.

Resolve confirmation

And now we need to somehow deal with closing dialog and getting a callback from the consumers. Here was used Promise based API, but it is possible to make it works using a callback style. In this example, once the user accepted or canceled the alert, your awaiting promise will be resolved or rejected.

To do so we need to save Promise's resolving functions and call them on appropriate user action. React's ref is the best place for that.

  const awaitingPromiseRef = React.useRef<{
    resolve: () => void;
    reject: () => void;

  const openConfirmation = (options: ConfirmationOptions) => {
    return new Promise((resolve, reject) => {
      // save the promise result to the ref
      awaitingPromiseRef.current = { resolve, reject };

  const handleClose = () => {
    // Mostly always you don't need to handle canceling of alert dialog
    // So shutting up the unhandledPromiseRejection errors 
    if (confirmationState.catchOnCancel && awaitingPromiseRef.current) {


  const handleSubmit = () => {
    if (awaitingPromiseRef.current) {


That's it! Our dialog machine is almost ready! One thing is left — create a custom hook for better readability

export const useConfirmationService = () =>


You can easily customize dialog content by passing additional variant prop. Just add it to the ConfirmationOptions

export interface ConfirmationOptions {
  variant: "danger" | "info";
  title: string;
  description: string;

And render different dialog content as you wish.

    {variant === "danger" && (
        <Button color="primary" onClick={onSubmit}>
          Yes, I agree
        <Button color="primary" onClick={onClose} autoFocus>

    {variant === "info" && (
      <Button color="primary" onClick={onSubmit}>

Are you ready?!

Are you ready kids?!

Here is the final working example. Feel free to just steal the implementation of ConfirmationService.tsx file if you want to. This is pretty standalone and isolated logic of what we were talking about.

P.S. No burritos were harmed in the making of this article

Posted on by:

dmtrkovalenko profile

Dmitriy Kovalenko


Lazy developer. Typescript | Reasonml lover. ❤️ OSS


markdown guide


I have used this technique for 2 past React projects before ✌️✌️✌️

I used a global hook state manager that I created (github.com/devhammed/use-global-hook) then renders my custom Material UI Dialog component near routes in App.js then all I have to do is to call the showModal action (I use React.useReducer) whenever I need to:

  title: "Hello",
  content: (<Typography>Hi</Typography>),
  actions: [] // buttons

Hi there! Nice solution. It throws an error when you click in either cancelo or accept button of the dialog...

proxyConsole.js:64 Warning: Failed prop type: The prop children is marked as required in ForwardRef(DialogTitle), but its value is undefined.
in ForwardRef(DialogTitle) (created by WithStyles(ForwardRef(DialogTitle)))
in WithStyles(ForwardRef(DialogTitle)) (at ConfirmationDialog.tsx:34)
in div (created by ForwardRef(Paper))
in ForwardRef(Paper) (created by WithStyles(ForwardRef(Paper)))
in WithStyles(ForwardRef(Paper)) (created by ForwardRef(Dialog))
in div (created by Transition)
in Transition (created by ForwardRef(Fade))
in ForwardRef(Fade) (created by TrapFocus)
in TrapFocus (created by ForwardRef(Modal))
in div (created by ForwardRef(Modal))
in ForwardRef(Portal) (created by ForwardRef(Modal))
in ForwardRef(Modal) (created by ForwardRef(Dialog))
in ForwardRef(Dialog) (created by WithStyles(ForwardRef(Dialog)))....


Auto answering this.... changing this line solves the problem.

<DialogTitle id="alert-dialog-title">{title ? title : ""}</DialogTitle>

This is actually a really cool way to handle confirmations. The only minor problem is, when you press "agree" or "cancel", dialog content disappears just before the exit animation of the dialog completes. It creates some sort of a flickering effect. You need to watch carefully to see it, but if your exit animation duration is higher, you will end up with an empty dialog slowly fading away :)

Other than that, real cool way for confirmations and simple info dialogs!


Yeah, I'm not sure but looks like to solve this issue you need to reset confirmationState on material-ui`s Dialog onExited callback. And on close/submit just set "open" prop to false.


So here is the fix of "flickering" effect which was caused by resetting the state before dialog is faded out.


I know it's a bit late but thanks for the post, I found it really helpful! I was wondering whether or not using this service across multiple components would trigger a rerender for any component using the context any time a component called the confirm function and it seemed like it did. I added a useCallback around the openConfirmation declaration (with a setConfirmationState dependency) and it seemed to do the trick. Can anyone verify that this is the right way to go about this?


Thanks, clear and concise. I’d like to try this.


This use react hook and does that mean we can only use this in function component not class component?


Just in case you're still wondering, class components can't use hooks.


I had problems to understand all the code, .tsx parts got me confused. Do you have this code shared on some repo? I really want to use this solution.



You can find the code in the embedded sandbox in the article,
but here is a direct link codesandbox.io/s/neat-dialogs-3h5ou


Great code! Thanks for sharing this, helped me alot geeting global modal functionality together.