Fix workaround with GitHub latest styles #28
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR did various changes to make it work with the latest styles from GitHub.
light
section here: https://cdn.jsdelivr.net/npm/github-markdown-css@5.4.0/github-markdown.cssmarkdown-alert-note
markdown-alert-title
octicon-info
mr-2
to the ALLOW_CLASS set.@container
to make it able to parse GitHub CSS again.To read the output diff:
Next steps:
As I mentioned in #27, GitHub will use newer CSS syntaxes from now on -- they are using
@container
, maybe the next is@layer
or even CSS nestings. We need not a workaround but a solution to parse these new CSS syntaxes. Maybe integrating lightningcss, or making a fork of thecss
module to add supports (it is not updated for 2 years).