Global setup options on the service registration about razor.sweetalert2 HOT 17 CLOSED

This feature has been added in the v5.0.0 release. (#1446) (#1437)

See the README for more details.

from razor.sweetalert2.

This is an interesting suggestion. I'll consider it for the next major version to coincide with sweetalert2@11.

For now, I'd recommend using the Swal.Mixin({}), as this is the sort of use case it was created for. Swal.Mixin({}) creates a SweetAlertMixin object that you can call FireAsync() off of, with whatever options you pass in when the mixin was created.

from razor.sweetalert2.

How does Swal.Mixin({}) affects the current swal?

I used Swal.Mixin({}) yesterday and it works but makes useless the SweetAlertService current instance since SweetAlertService doesn't hold the option set up on SweetAlertMixin

from razor.sweetalert2.

I am using hardly the SweetAlertService and this would make me go a fix it over thousand of files. It doesn't seems a good way for me. 😢

from razor.sweetalert2.

Something you could try perhaps. Create your own scoped service called HeightAutoFalseSweetAlertService or something similar.

Inject my SweetAlertService in the constructor. Create the mixin you want. Store it in a local variable of the service class. Then create a FireAsync method that just passes the config object through to your mixin.

Then, in your components, replace @inject SweetAlertService Swal; with @inject HeightAutoFalseSweetAlertService Swal;

It could look something like this

public class HeightAutoFalseSweetAlertService {

  private SweetAlertMixin _heightAutoFalseMixin;

  public HeightAutoFalseSweetAlertService(SweetAlertService originalSwalService)
  {
      _heightAutoFalseMixin = originalSwalService.Mixin(new SweetAlertOptions {
        HeightAuto = false
      });
  }

  public async FireAsync(SweetAlertOptions options) {
    await _heightAutoFalseMixin.FireAsync(options);
  }
}

from razor.sweetalert2.

I see but still needs to be replaced on all components.

Why can't we have that mixing option in the services.AddSweetAlert2();?

I haven't read all the source code but does this will take huge refactorization?

This is what we need to expose

from razor.sweetalert2.

I won't be exposing that method, as I have no intention of extending the API beyond what is provided by the sweetalert2 library.

I'll look into being able to set defaults at Startup, but that will come with v5

from razor.sweetalert2.

I took a deep look into the source code.

I think we just need to overload AddSweetAlert2 with SweetAlertOptions and SweetAlertService constructor with SweetAlertOptions and chain down those settings.

from razor.sweetalert2.

@Basaingeal The MVP!

from razor.sweetalert2.

The global options are not working it's still setting the auto height on the body 😢.

from razor.sweetalert2.

Can you share the method call that is resulting in this? Your FireAsync call and the SweetAlertOptions that are being passed in?

from razor.sweetalert2.

await SweetAlertService.FireAsync(null, ResourceManagerLocalizer[Response?.Response?.Message ?? "TransactionCompletedSuccessfully"], SweetAlertIcon.Success);

from razor.sweetalert2.

from razor.sweetalert2.

I am not passing any options at all I am using the overload method with only title, message and icon.

from razor.sweetalert2.

Yes. That is documented functionality. If you don't call the method with an options object on the C# side, it won't call the method with an options object on the JavaScript side.

For example Swal.FireAsync("Hello World") in C# interpolates to Swal.fire("Hello World") in JavaScript, while Swal.FireAsync(new SweetAlertOptions("Hello World") in C# will interpolate to Swal.fire({title: "Hello World"}) in JavaScript. If you call a method that doesn't use options, no default options can be applied.

from razor.sweetalert2.

I see. Will try again tomorrow.

from razor.sweetalert2.

It worked! Thanks!

from razor.sweetalert2.