Skip to content
New issue

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

Make ReactSweetAlertOptions type signature public, like SweetAlertOptions #208

Closed
emeth- opened this issue Aug 17, 2022 · 1 comment
Closed
Labels

Comments

@emeth-
Copy link

emeth- commented Aug 17, 2022

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?

github-actions bot pushed a commit that referenced this issue Aug 17, 2022
## [5.0.3](v5.0.2...v5.0.3) (2022-08-17)

### Bug Fixes

* export type ReactSweetAlertOptions (closes [#208](#208)) ([b3564da](b3564da))
@limonte
Copy link
Member

limonte commented Aug 17, 2022

🎉 This issue has been resolved in version 5.0.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

limonte pushed a commit that referenced this issue Nov 6, 2022
## [5.0.3](v5.0.2...v5.0.3) (2022-08-17)

### Bug Fixes

* export type ReactSweetAlertOptions (closes [#208](#208)) ([8a9fa8c](8a9fa8c))
limonte pushed a commit that referenced this issue Nov 7, 2022
## [5.0.3](v5.0.2...v5.0.3) (2022-08-17)

### Bug Fixes

* export type ReactSweetAlertOptions (closes [#208](#208)) ([8a9fa8c](8a9fa8c))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants