This repository has been archived by the owner on Nov 27, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 165
No destroy? #25
Comments
Yeah, this would probably be a nice thing to have. Will try to get to it as soon as I've got some time for OSS stuff. |
+1 Thoughts on this? |
@erik5388: I'm in the middle of a move and job change right now. I'm hoping to do a FancySelect revamp at some point, but can't quite yet! |
@paulstraw congrats on the move (I hope)! Of all the non-framework specific components out there I find fancy select to be my favorite. I'd love to help out when the time comes to revamp. Until then, best wishes to you and your move 😄. |
@paulstraw Any update on this issue? I'm having an issue where I have repeatable input sections and when adding new select menus I can't bind fancySelect to them. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've recently come across a situation where I need some kind of
.fancySelect('destroy')
.Have I missed something or is there no such option available as of now?
The text was updated successfully, but these errors were encountered: