[Feature] Edit the global default settings

[t4t5]

[Feature] Edit the global default settings

[t4t5]

Currently, lines 191-203 in sweet-alert.js are the ones holding the default parameters like this:

var params = {
  title: '',
  text: '',
  type: null,
  allowOutsideClick: false,
  showCancelButton: false,
  closeOnConfirm: true,
  confirmButtonText: 'OK',
  confirmButtonColor: '#AEDEF4',
  cancelButtonText: 'Cancel',
  imageUrl: null,
  imageSize: null
};

Couldn't you just change this so that it fits your project? I don't think there's a need to add an additional place where you can set the defaults.

[pomartel]

Yes, I saw that but the params variable is not public so I cannot extend it from the outside. It would be nice if this could be changed the way jQuery UI does it for exemple. You would just have to expose the params hash so it can be extended from outside the plugin.

I can give it a try on a pull request if you feel this is something others could benefit from.

[alkrauss48]

I agree with @pomartel, the ability to set default options outside of the plugin file would be cool. Having to edit the lib file makes updates more tedious, and prevents the ability to use a public CDN. Currently I'm just handling it with a function that has default attributes, merges in the custom attributes from the parameters, and calls swal. It works, but would be cool to have it baked in!

Great plugin, this seriously makes UI much more awesome.

[zzarcon]

Guys what do you think about #139? This PR adds the feature (which I think it's a powerful feature) to set a default user params without changing the source code or exporting some variables to global scope, you just have to call the setDefaults method.

[pomartel]

@zzarcon yes, I think your implementation is better than mine. Let's hope it gets merged!

[zzarcon]

@pomartel thanks man! Right now I'm waiting some feedback of @t4t5. I also hope that this will be merged because it's very tedious to pass the defaults parameters for each new alert :)