using (confirm) inside ngFor ? about ngx-sweetalert2 HOT 2 CLOSED

Hello @kudsyf, interesting issue. I'd be happy to reproduce, but:

• You don't show where the closing </li> is, so I don't know if the <swal> is comprised in the *ngFor here. Can you fix your code sample?
• A potential problem I see: You have a delete() function in your TypeScript, but your swal is also named delete. There's possibly a conflict here. Try to name your <swal> "deleteSwal" or something like that first.

edit: woops, edited your message to fix the mardown but I may have accidentally added the </li> after having copy-pasted the code in my IDE to fix the indentation. Or was it here before and I missed it? I don't know as I can't see your original post anymore, sorry :/

from ngx-sweetalert2.

Hello again,

After reading this issue again, I immediately understood what's the problem. The thing is that each [swal] will subscribe to confirm/cancel events of the same <swal> instance. So the behaviour you've encountered make perfect sense. Each entry will subscribe to the same modal and all of them will receive the same confirm/cancel events.

This is logical but definitely not practical. I've released a new version where multiple [swal] directives are now maintaining a "mutex" subscription to the shared <swal> instance. This will give the expected behaviour.

Please upgrade you ngx-sweetalert2 version:

3.3.1 (2018-02-14)

Bug Fixes

• SwalDirective: SwalDirectives now do a "cooperative mutex" when subscribing to an existing SwalComponent instance (#40) (19bc9c3)

from ngx-sweetalert2.