We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
b3564da
chore(release): 5.0.3 [skip ci]
b4e6f49
## [5.0.3](v5.0.2...v5.0.3) (2022-08-17) ### Bug Fixes * export type ReactSweetAlertOptions (closes [#208](#208)) ([b3564da](b3564da))
🎉 This issue has been resolved in version 5.0.3 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
fix: export type ReactSweetAlertOptions (closes #208)
8a9fa8c
9101c71
## [5.0.3](v5.0.2...v5.0.3) (2022-08-17) ### Bug Fixes * export type ReactSweetAlertOptions (closes [#208](#208)) ([8a9fa8c](8a9fa8c))
3c83d44
51f7be0
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: