-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: migrate to shikiji
#27
Conversation
Looks perfect, only one thing seems missing in shikiji. I think this feature should implement in shikiji. |
Oh yeah, it was in my backlog, I will check |
.filter(color => color !== 'default') | ||
.map(color => [ | ||
`html.${color} .shiki,`, | ||
`html.${color} .shiki span {`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if we should make this tiggering class configureable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We had this for a long time, let's keep it and will might drop it in a major version.(otherwise we will introduce breaking change in content)
Ok, font-style fixed |
close #25
Migrating to
shikiji
provides a few benefits.shikiji
useshast
internally, so we can get rid of the conversation codeshikiji
has multiple themes supported built-in (actually very similar to what we have here!), allowing us to reduce the complexitymdc
grammarThis might be a minor breaking change to the internal types and structure, but it shouldn't affect end users' code base.