Max number of notification about angular-toastr HOT 10 CLOSED

I don't know. I don't think the original one does it, but I have to diverge anyway.

What's the use case? I mean, I don't usually start pooping up hell of toasts :P

from angular-toastr.

I think it can be useful for me ;D
Maybe i use toast misused, but i have hell of toasts.
I show "info" toast, when user doing some unauthorised actions.

from angular-toastr.

I too would like to have this option. I have to keep the timeout a longer to make sure the error messages don't get skipped from user notice and my app can produce a lot of toasts if the user is performing operations quickly. Any plans of including this option or any workaround you could suggest?

from angular-toastr.

I can add it, it is something trivial and won't hurt.

from angular-toastr.

Please do add it. Thanks in advance.

from angular-toastr.

Thinking twice @softengi @katmai7. What would be the idea when the maximum number of toasts is reached? Discard new ones? Remove the last one to put a new one? Queue them?

from angular-toastr.

I would suggest closing off the oldest toast and add the new one.

from angular-toastr.

This is done on 1.0.0-beta.1

from angular-toastr.

@Foxandxss I see that you added support to queue the new notifications. Could you make it configurable to support closing off the oldest toast, as well. If not, could you suggest how I can achieve the same, at my end?

from angular-toastr.

@softengi I am afraid that it doesn't support that. I tried, I really tried but I never get it right. Seems to be easy but there is always a race conditition of creating vs destroying and I couldn't get it right.

If you or anyone else wants to try it, send a PR.

from angular-toastr.