PrismJS 代码高亮主题如何统一 || How to unify the PrismJS code highlighting theme

[RylanBot]

「博客文章 / 评论预览 / 评论内容」这三个部分的代码配色方案完全不同，看起来太杂乱了。
是否支持自定义配置评论区代码高亮的 CSS 主题来源？

---

The code color schemes of the three parts of "Blog Posts / Comments Preview / Comments Content" are completely different and look too messy.
Is it supported to customize the CSS theme source for comment section code highlighting?

[Mister-Hope]

目前不支持，可以考虑

---

It is not supported at present, you can consider

[RylanBot]

「预览区域和实际评论」代码颜色有区别疑似是 Bug -> 两者生成的 Token 逻辑不同，导致着色差异。

[Mister-Hope]

先看文档，再来说什么『疑似bug』

---

First look at the document, then talk about "suspected bug"

[RylanBot]

不好意思...昨天发起讨论前已经尝试引入这个文档的实例，本来不起作用🤔，但今天重新调整了写法，配色确实统一了。

回到最根本的需求「自定义评论区代码高亮主题」 → 是否可以考虑不将 hightlight.scss 一起打包进入 @waline/client/style ，而是用户按需额外导入即可。如果不导入的话，其实评论区会同步应用网站自带 Prism 的主题，现在由于该 scss 产物的优先级太高了，无法被覆盖。

---

Sorry... I tried to introduce this instance of [document] (https://waline.js.org/cookbook/customize/highlighter.html) before launching the discussion yesterday. It didn't work at all🤔, but today I readjusted the writing method , the color scheme is indeed unified.

Go back to the most fundamental requirement "Customize the comment area code highlighting theme" → Can you consider not packaging highlight.scss into @waline/client/style, but importing additionally on demand by users. If you don't import it, the comments section will actually synchronize the theme of Prism on the application website. Now, because the priority of this scss product is too high, it cannot be overwritten.

[Mister-Hope]

Then it's at least a major breaking change.

As a work around, you can pack a style without highligh.scss yourself and use it.

[Mister-Hope]

A new issue as a feature request for this is welcomed, but we still need further discussion and RFCs for this.

I still think this is kind of edge case.

It's reasonable for Waline to pack a small size of code block theme to correctly displaying code block highlights, as there would be more users who don't have any prismjs styles in site. And I agree the point that this makes users even impossible to override