fix: compatibility with precss v3 #35
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
precss v3 replaced postcss-extend with postcss-extend-rule which uses different syntax
Owner
|
sweet action. syntax is not a problem, we just wanna better and clean UI/UX. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I didn't test 0d877f2 thorough enough. I only noticed it yesterday while working on #34 and wondered why the links on
archives/page doesn't highlight when hover in light theme.precss v3 replaced postcss-extend with postcss-extend-rule which uses different syntax.
I have looked through typing.css and should cover all post/precss plugins by now. Let me know if I miss any.
css values are lowercase.
https://weyusi.github.io/hexo-testing/archives/ has this commit.