-
Notifications
You must be signed in to change notification settings - Fork 117
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
Future of This Repository #131
Comments
@iStefo I recently found ember-power-select and was going to take a look at it. If the community is moving toward this solution, I am happy to start using that and seeing if it satisfies my needs (style customization and lots of features). I don't want to maintain something that will become obsolete within a year. That being said, if there is a big following for this component, I'd be happy to help maintain this repo. I've worked with Ember and ED for almost 2.5 years now; most actively in the pre 1.0 - 1.7 versions but have recently started picking up the newest features in the latest versions for some large projects moving forward. |
@iStefo first of all thanks for putting together this addon and maintaining it all this while. It's really great! In my opinion if the feature set of the other plugin is the same as this one i'm ok with switching over. My only concern is that with this plugin you don't have to entirely worry about the actuall dropdown part at all as its maintained by the select-2 project. Since that project is HUGE you can assume it isn't going anywhere. The other project is ember specific and unless it becomes the standard it will always have a chance of fizzling out. |
Watching this project from the outside (as the primary maintainer of Select2), the Select2 4.0.0 upgrade is going to affect this project (along with others) in one of two ways:
Neither situation is really promising for this project, and as the maintainer of Select2 I'd hate to see this project fizzle out. But I'd also prefer seeing a functional component that works within the native ecosystem than a plugin which was forced into a corner and doesn't work well. |
So i'm guessing this has gone the way of the dodo. Unfortunately https://github.com/cibernox/ember-power-select doesn't support passing objects as content so its not quite a good replacement. |
ember-power-select also doesn't work easily if you put it inside your own addon. |
I finally pulled myself together and put a deprecation notice onto this repo. Without being able to support this addon within the scope of my work, there is no way I can invest an adequate amount of time to keep up with the issues that arise (and that have been piling up for over a year now). If anyone is interested in gaining access to the the repository, you are very welcome. |
I need to update this addon to Select2 4.0, do you give me access or transfer to me this repository? |
@clairton done! Thanks in advance for your efforts |
As you probably have noticed, I haven't spend any time to maintain this repository in the last months, and I'm very sorry about that.
ember-power-select (the future?)
Maybe you have already seen the https://github.com/cibernox/ember-power-select project, which aims at creating a select component that works similarly to Select2 but is implemented "natively" using Ember technologies.
The author of that component has kindly contacted me before starting with his work and asked for my opinion on his idea, and I was quickly convinced.The truth is: maintaining ember-select-2 sometimes is a real PITA because of all the edge cases, the huge API surface of Select2 and the permanent data conversion between the jQuery layer and the Ember layer. Implementing a similar component with native Ember code was, in fact, my long-term idea for this component anyway, and I'm glad that there are strong supporters for this approach, as you can see with the activity of the ember-power-select repo.
ember-select-2 (this component)
On the other hand, some of you have probably invested quite some time into integrating this component into their apps, which is why I understand that some people would like having this project a little longer.
If you feel ready to take over control over this repositories, please comment on this issue so we can discuss a way forward. Since it would probably be wise to have more than one person administrating this project, I am very open to invite multiple people to use this opportunity.
The text was updated successfully, but these errors were encountered: