I’m developing a theme component where I would like to do something similar to: [code] main() { printf("Hello World!\n"); } [/code] which yields: main() { printf("Hello World!\n"); } I’m using api.decorateCooked() for this, but since the content is already cooked all “redundant” space has been removed, e.g. the space before printf in the example above. How can I get access the “uncooked” text as the user entered it? To be clear; what I want to support with my theme component is to allow the user to write something like: [mytag] main() { printf("Hello World!\n"); } [/mytag] which my theme component understands and replaces with a transformation of the text within the [mytag] ... [/mytag].

To get access to raw you are going to need to use a plugin. What you can do though is use the wrap helper, that way you have a div to work with. [wrap=test] hello world [/wrap] Renders to: hello world

Thanks. Is it possible to install a custom plugin in a Discourse instance hosted by Discourse on a free plan? I haven’t found out how anyway. Would it be possible to implement support for raw for theme components? If so, would you accept a PR to do so? The wrap helper does not do what I asked for. It too removes indentation.

Sadly our free, standard and business tiers do not allow for custom plugins. We use a cluster that hosts many different customers we have no mechanism of running a plugin just for one customer. Supporting the ability to inject a markdown extension via a theme component is something I have thought about in the past, but we have no concrete plans to add it. It would be extremely hard to add. What about double wrapping? This will certainly keep all indentation. [wrap=test] ``` 1 1 3 ``` [/wrap] Maybe even just using something like this will work, you will have a distinct element to work with: ```custom test ```

Extremely hard also for you or just for someone like me without prior knowledge of the implementation? I what lies the hardness? Would it be easier to do something simpler than a full markdown extension such as read-only access to raw? Yes, this might be an option. Thanks.

[画像] magjac: Would it be easier to do something simpler than a full markdown extension such as read-only access to raw? The front end does not get the raw post content. It only gets the cooked version. This means that payloads to the client are smaller. On top of that the server is ultimately responsible for the markdown → html conversion. If we did this all at runtime on the browser we would be adding a lot of extra costs and have complicated security vectors to worry about.

@sam Thanks for your help. Your suggestion turned out well and gave a pretty decent syntax for the user as well: [Screenshot from 2020-05-04 13-40-01] :sunglasses:

Just to be clear, you do know that if what you really want is coffee blocks you can wrap code blocks with three back ticks, right? I can’t tell to what degree your example is a metaphor.

@pfaffman I don’t know what you mean by coffee blocks, but yes, I do know that three backticks generate a code block. I don’t know why my example should be a metaphor. For what? The image I posted is a screenshot to show what my theme component generates for the given code.

Sorry. coffee and code are almost the same on my mobile keyboard. It got them wrong every time when I wrote they sentence! I have looked and looked and I don’t see from your example what is different between your image and a standard code block.

The graph that my theme component has added.

テーマコンポーネントから未加工のコンテンツにアクセスする方法は？

開発

pfaffman (Jay Pfaffman) 2020 年 5 月 4 日午後 12:36 14

また、Discourse Graphviz がありますが、プラグインをインストールできないため、おそらくあなたの問題は解決しないと思います。

トピック		返信	表示
Working with different needs in raw/cooked content Development	7	5451	2025 年 5 月 15 日
BBcode color tags in a theme Development	12	2943	2023 年 9 月 1 日
Get back the real "raw" data that created a post? Development	33	4038	2026 年 1 月 24 日
Link to raw markup for topic / message Product Support	2	557	2024 年 2 月 2 日
Theme-Component v Plugin: What's the difference Development	22	6157	2020 年 6 月 9 日

テーマコンポーネントから未加工のコンテンツにアクセスする方法は？

関連トピック