Unable to pass arbitrary attributes into the trigger

I need to pass a data-test-... attribute into the trigger.

Looks like this is impossible to do.

Please pass splattributes (or some pre-Octane equivalent) into the trigger.

Or give the wrapper component a tag.

[lolmaus]

@cibernox In the mental model of any user who’s not got elbow deep into the ember-power-select source, is different from yours. What new Power Select users see is a component:

<PowerSelect>
</PowerSelect>

They don’t see a “trigger”, a “content”, a “wormhole”, whatever. They see a component called PowerSelect.

And every new user has an expectation that applying attributes on it will work. This is how every component in the Ember ecosystem works, and Power Select is probably the only one that breaks the expectation — and does so without warning. The behavior of dropping attributes/splattributes/modifiers is not documented, so you need to research its source to learn that <PowerSelect> is tagless and does not pass splattributes to the rendered component (Trigger).

Why does it not pass attributes to the rendered component? Because ideally you should be able to apply splattributes to the Content component, so… you get nothing?

Yes, trigger and content elements customization are also legit cases, but passing attributes to the Power Select component itself (what you call Trigger under the hood) is a much, much more common necessity.

I don’t see how a feature request for customizing the Content prevents from solving a source of pain for many Power Select users.

---

I’m speculating here, but I believe that every ember-test-selectors user who needed to acceptance-test a Power Select has spend at least two hours on this problem. And ember-test-selectors has ~250 000 installs per month, so that’s a lot of hours of frustration.

And ember-tests-selectors is just one of many reasons why you need attributes/modifiers on a Power Select. There are many more.

---

Also please note that there is a RFC in progress called “Splat Areas”: https://github.com/emberjs/rfcs/issues/517. It aims to solve the same problem that you pointed out, but in a more general way. It’s in an early stage, but still I believe it makes little sense to undertake a custom solution when a general solution is on the way. We should rather join forces over the RFC.

Please see if the RFC issue in its current way satisfies your needs. If it doesn’t, please express what it’s lacking and why, and suggest an alternative implementation if you can. If it does satisfy you needs, please encourage to promote it into a PR.

[rwwagner90]

This issue is blocking ember-bootstrap-power-select as well https://github.com/kaliber5/ember-bootstrap-power-select/issues/93. Anything I can do to help fix things? If the PR @lolmaus opened works, I would love if we could get it merged!