-
Notifications
You must be signed in to change notification settings - Fork 37
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 :line-numbers=number
supports
#161
Conversation
Pull Request Test Coverage Report for Build 9280691180Details
💛 - Coveralls |
can we split these 2 changes? |
I moved the attribute migration to another PR. |
@@ -229,7 +229,6 @@ div[class*='language-'] { | |||
padding-top: 1.3rem; | |||
font-size: 0.875em; | |||
line-height: $line-height; | |||
counter-reset: line-number; |
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.
239-242 should be removed?
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.
Do not remove, currently using counter-increment
for line numbering.
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 think its ok for you to use actual numbers like vitepress.
By this, the line number is coupled with an outside style.
But if we want the style built-in, then I think this should be fine.
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.
When writing numbers into the DOM, plugin-seo
includes the numbers from line-numbers
in the og:description
, but it does not include the code blocks content
, which seems a bit strange. Perhaps plugin-seo
needs to make some adjustments.
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.
Please resolve the conflicts
Before submitting the PR, please make sure you do the following
close #123
).What is the purpose of this pull request?
Description