Aaron Chambers

@lukemelia said: > It (`ember-cli-deploy` name prefix) was designed originally to guarantee uniqueness by leaning on npm's unique package name requirements @ghedamat said: > ember-cli-deploy- was only required because of...

We could, when evaluating the inline plugin name, check for the `ember-cli-deploy-` prefix and if it exists, strip it. This would mean that, if someone tries to use inline plugins...

Hey @GavinJoyce I'm trying to understand the context behind the `menu/item-element` component and how it relates to the `menu/item` component. What's the rationale behind it and the need for the...

> I don't remember the details. I seem to recall it was needed to keep parity with the Vue version, something to do with needing to have the flexibility of...

> 👍 I'd be delighted to remove the `menu/item-element` if we can, it's a pretty ugly API. Yeh, I think we can. I can't see anything in the Vue component...

> Nice. It's possible that the Vue API changed since I last looked at it late last year. Absolutely. I get the feeling you started this repo when the headlessui...

Hi @edslocombe. Thanks for this. Fancy submitting s PR for the change?

My vote is for 3). I'd like to see the plugin providing a basic default set of blueprint selectors and the then the user can specify selectors that are merged...

PS - Love to have your contributions @jrjohnson. Thanks for taking this on. Happy to talk through these options more if you need.

Thanks @jamemackson So it seems to me there's no changes needs to ember-cli-deploy per se. But maybe this is more of an educational thing that we need to include in...