Upcoming post menu changes - How to prepare themes and plugins

[david (David Taylor)]

@bitmage

I celebrate the shift towards glimmer components. But this will take time, and there’s a lot of widgets that people need to work with in the meantime. So I think improving the visibility of widgets as mentioned above would likely make the transition period easier for everyone.

The removal of widgets has been underway for a couple of years, and we hope to finalize it in the next few months. So I don’t think we’ll be making any changes to the underlying system before then.

@bitmage

Another thing that would help in plugin development is to see an attribute on any root DOM element rendered by a component/widget which tells you what component/widget you are looking at.

Have you tried the Ember Inspector? I think it should solve the problem you describe, and will even show Ember components that aren’t currently rendering any DOM elements.

@bitmage

You use withPluginApi("1.34.0", ...)

As of very recently, this version number is not required. You can do

export default apiInitializer((api) => {

or

withPluginApi((api) => {

We’ll be getting the docs updated with that change soon. The modern preference for managing version intercompatibility is the .discourse-compatibility file which @Arkshine mentioned:

@Arkshine

Also, this feature can help: Pinning plugin and theme versions for older Discourse installs (.discourse-compatibility)