-
Notifications
You must be signed in to change notification settings - Fork 16
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
cat-select should not use ui-select2 as part of its "settings" interface. #12
Comments
at the time this was a design choice for several reasons:
if you have any ideas on how to prepare the api already for the switch to the component based ui-select without just adding another api break now, i'd be happy to add it to the project |
We/You should ask ourselves, which features(options) make sense for a component like cat-select, and which do we want to provide? When digging around in our code, most of the used ui-select2 options are:
Not so frequently used options are (actually each only once):
So taking this information, we could come up with the following suggestion:
as for "...was just passing along everything 1:1, therefor a direct access to the select2":
|
Reason:
The text was updated successfully, but these errors were encountered: