Handle CSS-comments better in the preprocess-function (PR 14963 follow-up) #14980
Conversation
This file contains 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
…w-up) This fixes another oversight, please see the updated tests.
Snuffleupagus
force-pushed
the
preprocessCSS-comments-2
branch
from
d1b10da
to
397f2e6
Compare
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/8ce2f4c31d949d7/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/8ce2f4c31d949d7/output.txt Total script time: 2.68 mins Published |
|
Out of curiosity, did you build and run on m-c in order to be sure that everything is ok ? |
Yes, I diffed the output of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes another oversight, please see the updated tests.