No support for SASS maps

[bryanrideshark]

We've encountered an error with Web Essentials and it's SASS compilation. It doesn't seem to understand SASS maps.

Is there a way to update the version of SASS that's used in the plugin, or at least know what it is so we can see what features are available?

[SinnerAir]

+1

[am11]

It doesn't seem to understand SASS maps.

What doesn't understand SASS' maps?

Please elaborate the issue.

[SinnerAir]

Example:
@each $header, $size in (h1: 2em, h2: 1.5em, h3: 1.2em) {
#{$header} {
font-size: $size;
}
}

from http://blog.sass-lang.com/posts/184094-sass-33-is-released

show error :
/*
Compilation Error occurred (see error list to navigate to the error location):
Error found:
*/

Sorry, my bad english :-)

[am11]

Oh! this is related to sass/libsass#394. @SinnerAir's issue would probably be fixed by libsass soon. However, as @akhleung suggested, iterating over maps is not supported by libsass, so it might take a while to arrive.

Once this is fixed, node-sass would quickly wrap it and release the package. Keep an eye on it!

For syntax highlighting issue, the next update of Visual Studio will probably add its support and other v3.3 features.

/cc @spadapet, yet another new SASS 3.3 feature struck again! 8-)

[spadapet]

@madskristensen, add "maps" to the backlog so that our SCSS parser can support it.

[madskristensen]

I've added it to the VS Web Team's backlog. Closing the ticket here