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

Parsing error when using extrapolated variable as extend name #313

Closed
micahgodbolt opened this issue Oct 16, 2015 · 6 comments
Closed

Parsing error when using extrapolated variable as extend name #313

micahgodbolt opened this issue Oct 16, 2015 · 6 comments

Comments

@micahgodbolt
Copy link
Member

Getting parsing errors when I try to use an extrapolated variable in a silent extend.

Warning: Parsing error at test/fixtures/test1.scss: Please check validity of the block starting from line #3 Use --force to continue.
$var: 'foo';

%#{$var} {
  font-size: 18px;
}
@bgriffith
Copy link
Member

Hey @micahgodbolt - thanks for the issue. It's being caused by the parser so I've added an issue. Here's a reference tonyganch/gonzales-pe#110

@DanPurdy
Copy link
Member

Confirmed as working in gonzales-pe 3.2.1

@danez
Copy link
Contributor

danez commented Feb 4, 2016

As far as I can see gonzales-pe >= 3.0.0 fixed the issue. When I look at the PR it seems you are preparing to upgrade to version 3.2 soon, right? Do you guys have any eta when this will be finished? Or maybe upgrade to 3.0.x before 3.2 if there are no so many breaking changes in it?

We would love to use sass-lint, but this bug keeps us from doing that.

@DanPurdy
Copy link
Member

DanPurdy commented Feb 4, 2016

3.0 contains as many breaking changes as 3.2.. there are still regressions in 3.2 that are going to need to be fixed before this is complete but fingers crossed! 3.2 still doesn't work correctly with other types of interpolation either.. As for an eta, whenever we get the time to work on it, i'm afraid i can't be any more specific than that.

Might be worth keeping an eye on this issue though, #495

@bgriffith
Copy link
Member

@micahgodbolt The parse error has been fixed in 1.6.

@DanPurdy
Copy link
Member

ping @danez too ^^

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

No branches or pull requests

4 participants