-
-
Notifications
You must be signed in to change notification settings - Fork 657
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(markdown): keep meta from fenced code block #1800
Conversation
β Deploy Preview for demo-blog-nuxt-content ready!
|
β Deploy Preview for nuxt-content ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
β Deploy Preview for demo-blog-nuxt-content 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.
LGTM π
@Qwertovsky do you mind fixing linter issues? |
Co-authored-by: nobkd <[email protected]>
The sample mentioned above using This is really unfortunate because I am currently facing the issue that no different highlighting is applied to the lines in brackets, e.g., |
@SimonScholz Update: Fix was released with |
β Type of change
π Description
Don't drop a info from fenced code
So
meta-info=val
will be accessible from the document tree after parsing. Propertymeta
will be next tolanguage
,filename
,highlights
.It can help to do other modifications with remark plugins, transformers, or ProseCode component.
π Checklist