Toast: add the "remove" method to close a specific toast message #4101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
|
Hi @clemvnt, Please see my comment; Could you write your feedback on the thread above? Thanks a lot! |
mertsincan
added
the
Status: Discussion
mertsincan
removed
the
Status: Discussion
|
Thanks a lot for your contribution! Best Regards, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1763
Hello!
First of all, thank you for your work.
I have a need where in a toast, there is a button that must execute a process and close the toast on which the user has clicked. I can't use the group mechanism because :
removeGroupmethod, all the toasts in the group close.This PR is based on #1395. On the original PR, it says that you were going to implement a simular solution but the discussion dates back to 2021. There's been no news since, so I'll take my shot with this PR. 😀
Let me know if I've missed anything or if you prefer another implementation.