Skip to content
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.

No destroy? #25

Open
rawksteady opened this issue Nov 28, 2013 · 5 comments
Open

No destroy? #25

rawksteady opened this issue Nov 28, 2013 · 5 comments
Assignees

Comments

@rawksteady
Copy link

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?

@paulstraw
Copy link
Owner

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.

@Zettersten
Copy link

+1

Thoughts on this?

@paulstraw
Copy link
Owner

@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!

@Zettersten
Copy link

@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 😄.

@goncalomarques
Copy link

@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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants