# Allow registrations of components as plugin outlets

**URL:** <https://meta.discourse.org/t/allow-registrations-of-components-as-plugin-outlets/53464>\
**Category:** Development\
**Created:** [Novembro 28, 2016, 3:11am UTC](https://meta.discourse.org/t/allow-registrations-of-components-as-plugin-outlets/53464 "2016-11-28T03:11:12Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [Novembro 28, 2016, 3:11am UTC](https://meta.discourse.org/t/allow-registrations-of-components-as-plugin-outlets/53464/1 "2016-11-28T03:11:12Z")

</div>

I am hitting an issue extending outlets in solved.

At the moment in core we have:

```plaintext
<ul>
    <li>{{#link-to 'userActivity.likesGiven'}}Likes Given{{/link-to}}</li>
   ...
   {{plugin-outlet "user-activity-bottom"}}
</ul>

```

Which we can easily change to:

```plaintext
<ul>
    <li>{{#link-to 'userActivity.likesGiven'}}Likes Given{{/link-to}}</li>
   ...
   {{plugin-outlet "user-activity-bottom" tagName='li'}}
</ul>

```

This helps somewhat as the outlets will be injected as LI elements but has a big flaw.

For my case I only want to show the “solved” link IF the user has more than 1 solution. However our current design allows no control over the “wrapping” element, nor no way to conditionally render.

@eviltrout perhaps we should allow components for plugin-outlets as well, eg:

```plaintext
export default Em.Component({
   pluginOutlet: 'user-activity-bottom'
}) 

```

Then when we sweep through outlets we can either render a templates or explicitly defined components?

---

_[View the full topic](https://meta.discourse.org/t/allow-registrations-of-components-as-plugin-outlets/53464)._