Allowing onDismiss for Toaster Toasts

[lupitadavila]

For the Toaster component, can we add onDismiss to the useToaster toast? Or is there a reason for not having it there, but allowing it when creating a Toast component?

We'd like to be able to push a toast to the toaster and have a callback that saves that the toast was dismissed in the backend without it disrupting the other toasts in the array.

[SiTaggart]

Hi @lupitadavila

Thanks for the question! You are absolutely spot on, this is totally an oversight on our behalf that we missed.

I'm thinking that you probably should just be able to add it to the object when you're pushing a toast to the toaster. Something like

const handleClick = () => {
  toaster.push({
    message: 'Selection was successfully saved to your profile',
    variant: 'success',
    onDismiss: () => {...}
  })
}

And all it is, is the same as onDismiss for an individual Toast component

Does that sound about right to you?

[lupitadavila]

Yes, that is the idea!

[lupitadavila]

If there is an estimate on timeline for us to track, that would be great. Thanks a bunch 🙏🏼

[TheSisb]

I'll try to get this fix in by early next week, if that works for you.

[TheSisb]

A PR is open here: #1818

[nkrantz]

@lupitadavila this PR has been merged!