Closed emeth- closed 2 years ago
sweetalert2 makes the SweetAlertOptions type signature public, which is great and useful.
sweetalert2-react-content does not make the ReactSweetAlertOptions type signature public.
Any chance you'd consider doing so, making the two libs consistent?
:tada: This issue has been resolved in version 5.0.3 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
sweetalert2 makes the SweetAlertOptions type signature public, which is great and useful.
sweetalert2-react-content does not make the ReactSweetAlertOptions type signature public.
Any chance you'd consider doing so, making the two libs consistent?