Shortly I will be merging a branch of Discourse into master that updates us to the latest stable version of Ember, which is 2.10. This is exciting because we’ve been behind Ember’s stable branch for a while and we’ve finally caught up! It also contains the Glimmer 2 template engine which is quite a …

Will it be exposed via the plugin api before ember-2.10 lands on master? I’d quite like to keep my user card/profile customizations as a site customization (rather than a full-blown-plugin), if possible

[image] LeoMcA: i before ember-2.10 lands on master? I’m afraid it’s too late. @eviltrout just merged it.

Give me a few minutes, I’ll add it to the plugin api.

Okay I’ve addeed a Plugin API (version 0.6) to register a connector class. If you’re writing a full plugin I recommend you don’t use this and let the connector class be automatically resolved, but if you’re using a customization this will work: Add PluginAPI for r…

Just to expand a bit, looks like if you want to set a class on wrapping component you would use: api.registerConnectorClass('user-profile-primary', 'my-connector', { setupComponent() { this.set('classNames', ['foo']); } }); With the new changes I am seeing a wrapping span @eviltrout which …

Unfortunately there’s no way to remove it. Maybe you can change the HTML to have two ul tags, where the second one is the outlet?

Unlike the posted example directory structure [image] eviltrout: my-plugin/connectors/user-profile-controls/my-connector.js.es6 I noticed that some plugins (eg, cakeday) are like my-plugin/assets/javascripts/discourse/connectors/user-profile-controls/my-connector.js.es6 I’m guessing the …

[image] Mittineague: I’m guessing the directory structure is not important as long as the folder is named “connectors” and the choice is up to preference. Yeah I realized a bunch of plugins did it one way or the other so both are supported. In the long term I’d like to standardize on one and …

I’m trying to port a plugin to work with the Ember 2.10 port… however it seems topic-list-tags outlets actually don’t get output at all? I thought the context field didn’t exist anymore but the code tells me otherwise, however even if I’m using inline templates from customizations nothing seems to c…

This should fix it: [image] Raw plugin outlets not looking in RAW_TEMPLATES in v1.7.0.beta11 bug This commit should fix it: https://github.com/discourse/discourse/commit/7c8095294d7296f0f27d4cb4066f1555fc8c2cbc I’ve also included a test to avoid this happening again. …

Important changes to Plugin Outlets for Ember 2.10

Development

eviltrout (Robin Ward) January 5, 2017, 4:51pm 17

This should fix it:

Topic		Replies	Views
Using Plugin Outlet Connectors from a Theme or Plugin Developer Guides how-to , code	12	18553	October 14, 2024
Developing Discourse Plugins - Part 2 - Connect to a plugin outlet Developer Guides plugin-guides , tutorial	38	29980	November 23, 2025
Using a Discourse component in a plugin Development	19	4549	January 26, 2017
Conditionally rendering a plugin outlet Development	4	2114	December 12, 2016
An interesting strategy for passing properties via raw template plugin outlets Development	4	959	January 18, 2022

Important changes to Plugin Outlets for Ember 2.10

Related topics