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
We're upgrading from 3.0.6 to 4.0.2.
We have this searchable power-select component, and we were using the {{else}} block for displaying custom html code when no results. After upgrading that block isn't showing anymore.
{{#power-selectsearchEnabled=truesearch=(queue
(action (mutsearchName))
(action (performsearchEmployeesFromLocationTask))
)
placeholder=" Type to search employees at other locations"labelPath="name"selected=changeset.namedisabled=disabledonChange=(actionupdateEmployee)
as |employee|
}}{{employee.name}}{{else}}
CUSTOM HTML CODE
{{/power-select}}
Apparently that was removed here. What's the suggested approach now? Or how could we get this {{else}} block back?
Thank you.
The text was updated successfully, but these errors were encountered:
At the moment the argument "noMatchesMessage" allows you to place simple text in there. If you need html code, you could write a custom modifier (https://github.com/ember-modifier/ember-modifier). Unfortunately a modifier can only be placed on the power select if it's rendered in place (it passes attributes to a basic dropdown which will only apply them if rendered in place). A solution to this would be wrapping the power select inside a div and placing the modifier on the div.
Yeah, we had to give up that feature when updating to glimmer components. You still can do it by overriding the optionsComponent, but it's very inconvenient. I hope that named blocks will allow us to reintroduce this feature.
We're upgrading from
3.0.6
to4.0.2
.We have this searchable power-select component, and we were using the {{else}} block for displaying custom html code when no results. After upgrading that block isn't showing anymore.
Apparently that was removed here. What's the suggested approach now? Or how could we get this {{else}} block back?
Thank you.
The text was updated successfully, but these errors were encountered: