-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
git-subtree-dir: src/libsass git-subtree-split: 39e3087
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.
Should this go against v5 branch?
@@ -47,7 +47,7 @@ int base64_encode_block(const char* plaintext_in, int length_in, char* code_out, | |||
*codechar++ = base64_encode_value(result); | |||
result = (fragment & 0x003) << 4; | |||
#ifndef _MSC_VER | |||
__attribute__ ((fallthrough)); | |||
/* fall through */ |
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.
This is an upstream thing, but it seems odd to have a compiler directive for only a comment now
@@ -126,12 +121,11 @@ namespace Sass { | |||
|
|||
namespace File { | |||
|
|||
static std::vector<std::string> defaultExtensions = { ".scss", ".sass" }; | |||
static std::vector<std::string> defaultExtensions = { ".scss", ".sass", ".css" }; |
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.
This seems off, is this the think where libsass was treating plain CSS as SCSS?
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.
This is the revert of the CSS import deprecation warning as discussed in #2362
This LibSass version bump in specifically to resolve #2362 so it needs to land in v4. |
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.
Think most of my comments here are for minor upstream things. I guess the idea is to get this in for a 4.12 before cutting a 5
Is this a complete revert of the CSS importing behavior or are there minor changes on how it works behind the scenes? |
This is a revert to the previous behaviour. There will be changes soon in
order to match the newly spec'd behaviour
…On Thu., 15 Nov. 2018, 5:09 am Ranie Santos ***@***.*** wrote:
Is this a complete revert of the CSS importing behavior or are there minor
changes on how it works behind the scenes?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2543 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWPCAY6TBRSSMO8aa8KtwaIFHW_8aks5uvFx1gaJpZM4YYVlc>
.
|
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.
Looks to me "libsass"
version key didn't get updated and the version "3.5.4" got embedded in the binaries... causing #2621
…indicator Make error indicator Unicode aware
src/libsass
with a git subtreeFixes #2362