Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Discrepancies between node-sass parsing and the ruby gem #35

Closed
gregtillbrook opened this issue Nov 5, 2012 · 2 comments
Closed

Discrepancies between node-sass parsing and the ruby gem #35

gregtillbrook opened this issue Nov 5, 2012 · 2 comments

Comments

@gregtillbrook
Copy link

Hi there, there seems to be some differences between node-sass and ruby gem regarding string handling.

e.g.
For desired css of the form;

background: url(/static_loc/img/beta.png);

I was able to write the following sass;

$base_url: "/static_loc/";
background-image: "url("#{$base_url}"img/beta.png)";

However, when I switched to the ruby gem (due to #33) I had to omit several quotes to get the same css;

$base_url: "/static_loc/";
background-image: url(#{$base_url}img/beta.png);

Not a massive issue (I can probably refactor it so it works for both) but I thought it'd help to raise an issue as I assume you folks want to keep all sass parsers in sync?

Cheers,
Greg

@andrew
Copy link
Contributor

andrew commented Nov 6, 2012

I suspect this is an issue in the underlying C library, libsass: https://github.com/hcatlin/libsass

Node-sass simply wraps libsass and provides an interface to it in javascript, I suggest you report the issue there.

@andrew andrew closed this as completed Nov 6, 2012
@gregtillbrook
Copy link
Author

Ah, of course. Thanks!

Have bounced the issue on to sass/libsass#58

Id guess this will be the same situation for #33 too?

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

No branches or pull requests

2 participants