Mandatory reject param?

Hi there!

I’m upgrading my code to v4, and I saw that the new reject(dismiss) Promise is mandatory to avoid browser errors. If I do not set a dismiss function, I get the following error in Chrome:

Uncaught (in promise) cancel

Would be possible to make this reject optional? Sometimes we just want to close the popup if the user hits cancel, and not show a new swal to confirm that the user clicked cancel successfully.

If I code an empty dismiss function just to avoid this error, ES6 linters will fire up to not create empty functions, and the code would not be accepted for deployment.

Best regards, Rafael.

[limonte]

@samturrell I implemented your suggestion in v4.0.6 https://jsfiddle.net/limon/2ya7akjq/

Thank you Sam, with your help we finally found the solution for this issue.

[samturrell]

The only way i can really see this being resolved is with an opt-in solution such as

Promise.prototype.done = function() {
    return this.catch(function() {
        // Silence is golden.
        // Catch promise rejections silently.
    });
};

And then swal().done() to suppress the error.

There is no way to fix this without using a non-native promise implementation where we can suppress the error internally.