You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thank you for this plugin, it is very light and get the job done quick.
I have one suggestion sir.
Its very common for web app to have recurrent messages (shown as toast), like errors occuring for the same reason (or related to), or steps in the app workflow that shows a toast for each step but it would be less overwhelming to override the previous toast if step get finished fast. Because it is related.
I would suggest to add an "id" property to the toast, optional of course, but if it is set and a toast already exists with the same id, immediately hide this previous toast and show new one.
I could try a PR if you agree that it could be a good addition.
The text was updated successfully, but these errors were encountered:
@Tucsky
Hi, thanks for the idea, yes you can try to send a PR, i would like to see your implementation first.
I would also like to see any existing similar toast plugin which does the same.
Well there was two plugin that pop out when I decided to add one to my app, vue-toasted and this one! I didn't actually checked to see if vue-toasted was doing the id feature before posting but just found out that it don't support that, which is surprising tbh.
Hello, thank you for this plugin, it is very light and get the job done quick.
I have one suggestion sir.
Its very common for web app to have recurrent messages (shown as toast), like errors occuring for the same reason (or related to), or steps in the app workflow that shows a toast for each step but it would be less overwhelming to override the previous toast if step get finished fast. Because it is related.
I would suggest to add an "id" property to the toast, optional of course, but if it is set and a toast already exists with the same id, immediately hide this previous toast and show new one.
I could try a PR if you agree that it could be a good addition.
The text was updated successfully, but these errors were encountered: