You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When power select is in multi select mode, the item that is generated contains the clear in an <li> element. While there is a selectedItemComponent, it does not include the <li> or the clear element. I would like to be able to conditionally change the background of the items.
Should there be other things added in the future (aria-labels maybe) should we change this to a single property to allow more customizable options to be added while only reserving one property name. For example
This would be a breaking change, but an or in the if would allow for backward compatibility. We could temporarily add a did-insert to the <li> element that could do a check and deprecate the disabled property until the next release and then remove.
Would be happy to do a PR an approval was given for which direction to take, respect a className property or create a powerSelectItem property and put className there and move disabled.
The text was updated successfully, but these errors were encountered:
When power select is in multi select mode, the item that is generated contains the clear in an
<li>
element. While there is a selectedItemComponent, it does not include the<li>
or the clear element. I would like to be able to conditionally change the background of the items.While I can not find this documented, the code does allow the option to contain a property
disabled
, see https://github.com/cibernox/ember-power-select/blob/master/addon/components/power-select-multiple/trigger.hbs#L9Could we extend this to a property named
className
perhaps to allow forShould there be other things added in the future (aria-labels maybe) should we change this to a single property to allow more customizable options to be added while only reserving one property name. For example
This would be a breaking change, but an
or
in theif
would allow for backward compatibility. We could temporarily add adid-insert
to the<li>
element that could do a check and deprecate thedisabled
property until the next release and then remove.Would be happy to do a PR an approval was given for which direction to take, respect a className property or create a powerSelectItem property and put className there and move disabled.
The text was updated successfully, but these errors were encountered: