You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Astro, we'd love to power our new built-in <Code> component with Shiki (to eventually replace our current built-in <Prism> component).
However, we would like to keep shikli as an implementation detail, and not leak the class="shiki" attribute onto the <pre> element if possible.
Is this something that you / the team is interested in adding as a configuration value to codeToHtml() to customize the <pre> class name that gets added? If so, I'm happy to provide the PR.
The text was updated successfully, but these errors were encountered:
I think I'd be cool with that being a configuration option like wrapperClasses of some sort, which is an array, with the default as ["shiki"]. Then you could pass in wrapperClasses: [] to not have any.
Extra win is that the default is something like: ["shiki", "$theme-name"] which adds the theme name OOTB so that the multi-render concept could be less work for other people too if they don't go the CSS vars route mentioned in #33
In Astro, we'd love to power our new built-in
<Code>
component with Shiki (to eventually replace our current built-in<Prism>
component).However, we would like to keep shikli as an implementation detail, and not leak the
class="shiki"
attribute onto the<pre>
element if possible.Is this something that you / the team is interested in adding as a configuration value to
codeToHtml()
to customize the<pre>
class name that gets added? If so, I'm happy to provide the PR.The text was updated successfully, but these errors were encountered: