-
Notifications
You must be signed in to change notification settings - Fork 462
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
Difference in interpolated function calls #1397
Comments
I've run some additional tests and it looks like there are quite a few failing cases which are all likely related to the originally reported issue. Here are six test cases, showing interpolation around a function call, and around a parenthesized expression. The first six declarations are the test cases themselves, the next six show the Input:
Ruby Sass
Libsass
|
IMHO the original issue can be boiled down to div {
color: foo(0); /* foo(0) */
color: #{bar}(1); /* bar1 */
color: #{b}az(2); /* baz(2) */
color: b#{a}r(3); /* bar(3) */
color: #{b}a#{z}(4); /* baz4 */
color: #{b}a#{z} (5); /* baz 5 */
} I guess the underlying reason is that an interpolation directly followed by a parenthese "stops" the parsing (seems like parentheses must be preceded by something identifier like). IMO it's related to the issues with "list is always space delimited". Not sure if ruby sass is correct here, but I think I start to see the pattern. |
Ruby Sass
LibSass
I'm not sure what the rationale behind this behaviour is. I've asked for an explanation upstream. However for the time being this is an inconsistency with an existing spec.
Spec https:/sass/sass-spec/tree/master/spec/libsass-todo-tests/libsass/interpolated-function-call
The text was updated successfully, but these errors were encountered: