You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the idea, but I'm not sure if it would be very helpful. When you call destroy() you usually have a context and know where it's being called from. This allows you to control any side effects quite accurately. Maybe you have code examples where it might be really helpful?
Would you accept a PR to add an
onDestroy
event?If you add external elements that interact with Air Datepicker, it's a good idea to also clean them up.
While nothing is stopping someone from just overriding the
destroy
method, it's cleaner to do it via an event.The event handler could be a void function and could be called right after the other event listeners have been cleaned up.
Thanks!
The text was updated successfully, but these errors were encountered: