Skip to content
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

invalid unordered_map<K, T> key #934

Closed
Haemoglobin opened this issue Mar 11, 2015 · 4 comments
Closed

invalid unordered_map<K, T> key #934

Haemoglobin opened this issue Mar 11, 2015 · 4 comments
Milestone

Comments

@Haemoglobin
Copy link

On node 0.12, Windows 7, with latest version of gulp-sass
The following works:
$map: (
test: 1
);

The following FAILS:
$map: (
notest: 1
);

If you have a sass map, where a key in the map starts with 'no' - then you will see the following error:
invalid unordered_map<K, T> key

What would cause this? Can this be fixed but even better could the error give more information?

Thanks,
Hamish

@xzyfer
Copy link
Contributor

xzyfer commented Mar 11, 2015

Thanks for the report Hamish. This is a bug with the not keyword. It's
fixed and will be in the 3.2.0 release.

For now quoting the key might work.
On 11 Mar 2015 20:32, "Haemoglobin" notifications@github.com wrote:

On node 0.12, Windows 7, with latest version of gulp-sass
The following works:
$map: (
test: 1
);

The following FAILS:
$map: (
notest: 1
);

If you have a sass map, where a key in the map starts with 'no' - then you
will see the following error:
invalid unordered_map key

What would cause this? Can this be fixed but even better could the error
give more information?

Thanks,
Hamish


Reply to this email directly or view it on GitHub
#934.

@KittyGiraudel
Copy link

Actually it does not come from no but from a bit too agressive handling of the not keyword. Another reason to quote your strings (although there is still a bug to be fixed). :)

@mgreter mgreter added this to the 3.2 milestone Mar 11, 2015
@Haemoglobin
Copy link
Author

Thanks for the fast reply - and putting the keys in as strings works great as a workaround :)

Cheers

@mgreter
Copy link
Contributor

mgreter commented Mar 11, 2015

Going to close this since it seems to be already resolved on master and it is currently the last open issue in our 3.2 Milestone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants