-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Named colours don't work as map keys #652
Comments
Confirmed! I get the following (JSON) error from libsass, with the new API implemented in node-sass (unreleased): {
"status": 1,
"path": "c:/temp/foo3.scss",
"line": 18,
"column": 13,
"message": "argument `$map` of `map-get($map, $key)` must be a map\nBacktrace:\n\tc:/temp/foo3.scss:18, in function `map-get`\n\tc:/temp/foo3.scss:18, in function `palette`\n\tc:/temp/foo3.scss:24"
} @mgreter, separately; in |
|
Any solution yet? |
I've added this to the 3.0.3 milestone it should make it into the next release. |
It appears my initial thoughts were wrong. The issue is because the map key is a color name. Libsass has some issues when it comes to parsing strings that are color names i.e. #558 Reduced case: http://sassmeister.com/gist/d2be1def3619bd6c3a54 |
As a heads up, it looks like the user may be running in to the issue related to sass/sass#363 in that colors as map keys aren't strings, but colors. |
I believe this is somewhat true. I think the map key is being treated as a colour rather than a string, although I'm not sure why this is a problem. It's worth noting the reduced test case works fine on Ruby sass. |
The issue is that we're treat I've got a fix I'll ship in a couple hours. |
Hi all,
I'm trying to implement a colour palette function seen in this article here.
http://erskinedesign.com/blog/friendlier-colour-names-sass-maps/
This is the resulting code
All signs seem to point to this working but I get this error.
I'm using Grunt Sass version - 0.16.1
Any ideas?
Many thanks
The text was updated successfully, but these errors were encountered: