-
-
Notifications
You must be signed in to change notification settings - Fork 416
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: add handling for FontStyle.Strikethrough
#976
Conversation
✅ Deploy Preview for shiki-matsu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for shiki-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Oh nice catch! LGTM. Anything left for it to be ready? |
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.
It was actually pointed out to me by @hippotastic in expressive-code/expressive-code#316.
|
||
.vp-code, | ||
.vp-code span { | ||
/* background-color: var(--shiki-bg, inherit); */ |
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.
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.
FontStyle.Strikethrough
FontStyle.Strikethrough
FontStyle.Strikethrough
FontStyle.Strikethrough
Description
This PR adds support for handling the
FontStyle.Strikethrough
in a few places where it was not present. The primary motivation was to support ANSI strikethrough which is supported by the underlyingansi-sequence-parser
package but not by Shiki.Linked Issues
Fixes #975 by myself
Additional context
I would appreciate any help in pointing out the new test cases which should be added to cover the changed code (and where to add them).