As part of our continuous effort to improve the Discourse codebase, we’re removing uses of the legacy “widget” rendering system, and replacing them with Glimmer components. Recently, we modernized the post menu , and is now available in Discourse behind the glimmer_post_menu_mode setting. This set…

We’ve switched the Glimmer Post Menu to enabled by default. Once your Discourse instance is upgraded, this will cause existing customizations that weren’t updated to the new API to not be applied. For now, admins can still change the setting back to disabled while getting the remaining customizati…

I appreciate the flexibility of having the full component API available. I like the syntax of glimmer components overall, and I see why it may have benefits in reducing complexity within the codebase. However, for basic use cases (I want to add a button and give it an icon), the old API methods we…

Also, if I want to only implement the new functionality, what Discourse API version should I peg my plugin compatibility to? You use withPluginApi("1.34.0", ...) in all of your examples. I think this is an older version and not representative of when this change was made? But please clarify. Tha…

[이미지] Brandon Mason: You use withPluginApi("1.34.0", ...) in all of your examples. I think this is an older version and not representative of when this change was made? It’s the correct version. You can look at the changelog here: https://github.com/discourse/discourse/blob/main/docs/CHANGEL…

[이미지] Brandon Mason: 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 everyon…

[이미지] David Taylor: As of very recently, this version number is not required. This is actually really nice! Every time I forget to update that number :rofl:.

@david @Arkshine wow, great posts, really helpful! Another question - regarding the “context” that is shared when calling api.registerValueTransformer, how can I find out what context is going to get passed to me? I suppose I can just console.log the context, but it would be nice to know before ha…

[이미지] Brandon Mason: Another question - regarding the “context” that is shared when calling api.registerValueTransformer, how can I find out what context is going to get passed to me? I’m afraid we don’t currently have any central documentation for these. Some areas of the app have their own …

Searching “applyTransformer” returns 0 results . Am I looking in the wrong place? I do find that searching for “api.registerValueTransformer” returns some helpful examples . But of course the examples don’t provide comprehensive documentation of the context being returned - they only show the ones …

Oh, I think I answered my own question. This example shows use of api.getCurrentUser(). So essentially that portion of the API hasn’t changed, and is still compatible with the glimmer paradigm.

예정된 게시글 메뉴 변경 - 테마와 플러그인 준비 방법

개발

david (David Taylor) 4월 1, 2025, 3:05오후 19

The legacy post menu code has now been removed. Thanks to everyone who worked on updating their themes & plugins

글		댓글	조회수
Upcoming post stream changes - How to prepare themes and plugins Development dev-news	12	1758	11월 27, 2025
Updating Discourse Plugins, taking the first step Development	12	3920	3월 22, 2016
Upcoming Header Changes - Preparing Themes and Plugins Development dev-news	36	4285	9월 8, 2024
A versioned API for client side plugins Development rest-api	33	20271	6월 21, 2024
Upcoming topic-list changes - how to prepare themes and plugins Development dev-news	35	2355	4월 14, 2025

예정된 게시글 메뉴 변경 - 테마와 플러그인 준비 방법

Related topics