{"action":"created","issue":{"url":"https://api.github.com/repos/limonte/sweetalert2/issues/125","repository_url":"https://api.github.com/repos/limonte/sweetalert2","labels_url":"https://api.github.com/repos/limonte/sweetalert2/issues/125/labels{/name}","comments_url":"https://api.github.com/repos/limonte/sweetalert2/issues/125/comments","events_url":"https://api.github.com/repos/limonte/sweetalert2/issues/125/events","html_url":"https://github.com/limonte/sweetalert2/issues/125","id":154062509,"number":125,"title":"Alert queues","user":{"login":"KHam0425","id":7086236,"avatar_url":"https://avatars.githubusercontent.com/u/7086236?v=3","gravatar_id":"","url":"https://api.github.com/users/KHam0425","html_url":"https://github.com/KHam0425","followers_url":"https://api.github.com/users/KHam0425/followers","following_url":"https://api.github.com/users/KHam0425/following{/other_user}","gists_url":"https://api.github.com/users/KHam0425/gists{/gist_id}","starred_url":"https://api.github.com/users/KHam0425/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KHam0425/subscriptions","organizations_url":"https://api.github.com/users/KHam0425/orgs","repos_url":"https://api.github.com/users/KHam0425/repos","events_url":"https://api.github.com/users/KHam0425/events{/privacy}","received_events_url":"https://api.github.com/users/KHam0425/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-10T17:28:23Z","updated_at":"2016-05-10T18:35:17Z","closed_at":null,"body":"Is there any way to incorporate a similar strategy that was used here (https://github.com/t4t5/sweetalert/issues/457) in SweetAlert2?  If I use the basic forms of swal2, everything works with the code those folks have contributed in that thread.  However, it seems to get tied up when I try to use strategies that incorporate a form in the callback function.  I think that SwalService doesn't know how to handle the promise resolution, or maybe it's how I'm calling it, I'm not sure.\r\n\r\nI'll continue to try to walk through different ways of making the swal() calls, but it would be great if an alert queue was built into this package without having to resort to outside plugins copied from an issue thread.\r\n\r\nIf there's anything I can do myself, or if there is a workaround that someone else sees, I'd be glad to do it another way."},"comment":{"url":"https://api.github.com/repos/limonte/sweetalert2/issues/comments/218249473","html_url":"https://github.com/limonte/sweetalert2/issues/125#issuecomment-218249473","issue_url":"https://api.github.com/repos/limonte/sweetalert2/issues/125","id":218249473,"user":{"login":"KHam0425","id":7086236,"avatar_url":"https://avatars.githubusercontent.com/u/7086236?v=3","gravatar_id":"","url":"https://api.github.com/users/KHam0425","html_url":"https://github.com/KHam0425","followers_url":"https://api.github.com/users/KHam0425/followers","following_url":"https://api.github.com/users/KHam0425/following{/other_user}","gists_url":"https://api.github.com/users/KHam0425/gists{/gist_id}","starred_url":"https://api.github.com/users/KHam0425/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KHam0425/subscriptions","organizations_url":"https://api.github.com/users/KHam0425/orgs","repos_url":"https://api.github.com/users/KHam0425/repos","events_url":"https://api.github.com/users/KHam0425/events{/privacy}","received_events_url":"https://api.github.com/users/KHam0425/received_events","type":"User","site_admin":false},"created_at":"2016-05-10T18:35:17Z","updated_at":"2016-05-10T18:35:17Z","body":"I'm currently working on an extension that parses user selections in a drop down menu.  Some of those selections have properties in their object that warn the user that one of the selections they have in the multi-select should be removed from the selected options, and includes the reason why they should be removed.  So, if you select 3 items from the drop down, the extension parses the selections, and returns an object with each item's properties within.  On object 1, there is 1 warning that the selected option is not allowed, and on object 3 there are 2 different warnings for the selected option.  Additionally, the warning allows the user to submit an override request that will enable selection, but will send a report that they have overriden the warning. \r\n\r\nSo, I need to queue an alert with the warning content so it goes through each object's warnings sequentially, instead of them randomly popping up when the next object construction completes, ie. \r\n`warnings.forEach(function(warning){swal(warning).then(function(isConfirm){if(isConfirm){swal({title: 'Override Request', html:$requestForm, preConfirm: function(result){return new Promise(blahblah){stuff; resolve(stuff)}}}).then(function(result){$processResult});`\r\n\r\nI hope this helps to explain one scenario where it makes sense to queue alerts and to process the queue one at a time until all are resolved.\r\n\r\n"}}