Is your feature request related to a problem? Please describe.
I have a situation where a custom Toast component is shown by a parent view (it performs long-running work), and that custom component is itself responsible for dismissing itself. This works fine, but currently there is no way for the
Describe the solution you'd likeToast.hide() should accept a callback that fires after the Toast is hidden/off-screen (presumably at the same time as the onHide() prop).
Describe alternatives you've considered
I was unable to properly pass props to handle this case. React Context may have been another way to go, but this seems silly given the Toast architecture.
Is your feature request related to a problem? Please describe. I have a situation where a custom Toast component is shown by a parent view (it performs long-running work), and that custom component is itself responsible for dismissing itself. This works fine, but currently there is no way for the
Describe the solution you'd like
Toast.hide()
should accept a callback that fires after the Toast is hidden/off-screen (presumably at the same time as theonHide()
prop).Describe alternatives you've considered I was unable to properly pass props to handle this case. React Context may have been another way to go, but this seems silly given the Toast architecture.
Additional context n/a