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

Any support? #1562

Closed
adamasantares opened this issue Aug 31, 2016 · 5 comments
Closed

Any support? #1562

adamasantares opened this issue Aug 31, 2016 · 5 comments

Comments

@adamasantares
Copy link

There are so many issues and no fixes. Please, let us know if this plugin hasn't support anymore...

@MrHubble
Copy link

MrHubble commented Sep 5, 2016

Apparently this project is no longer maintained as discussed here: #1424

It was recommended to use https://github.com/corejavascript/typeahead.js but that hasn't been updated for 8 months so I'm not sure if that's the best solution either.

https://github.com/algolia/autocomplete.js was also recommended and it has recent activity.

@bitcity
Copy link
Contributor

bitcity commented Sep 6, 2016

Feature-wise, there are a few better options

Both are a bit heavier than typeahead.js but have a lot more features like multiple select, pagination, infinite scroll, mobile support etc.
Select2 is slightly bigger than selectize.js and extending it is complicated in the current version (4.x). Hence I've found selectize.js to be a good replacement for my projects.

@adamasantares
Copy link
Author

adamasantares commented Sep 6, 2016

@bitcity thank you for links, but my problem is that the client's project uses this plugin and I can't change it to other plugin for now :(

@josephearl
Copy link

josephearl commented Sep 21, 2016

As someone who uses the library in a few projects I would highly welcome a canonical fork (ideally with a notice in this repo) in the hands of someone who has the time and energy to maintain this.

I'd also note to Twitter devs that it is much better for reputation and brand to pro-actively identify unmaintained projects and mark these as such clearly at the top of the README so the community knows it is OK to create a new canonical fork (and offering to include a link to that fork from your repo).

@adamasantares
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants