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

Parent selector (&) not supported in variable declaration #117

Open
dingo-d opened this issue Oct 12, 2018 · 4 comments
Open

Parent selector (&) not supported in variable declaration #117

dingo-d opened this issue Oct 12, 2018 · 4 comments
Labels
Milestone

Comments

@dingo-d
Copy link

dingo-d commented Oct 12, 2018

I'm getting a

Unable to parse file ... Parse error at line ...

And the error points to

$this: &;

the & character.

This is a perfectly valid SCSS syntax, how come it's throwing errors?

@racodond racodond changed the title SCSS scan parse error Parent selector (&) not supported in variable declaration Oct 15, 2018
@racodond racodond added the bug label Oct 15, 2018
@racodond racodond added this to the 4.19 milestone Oct 15, 2018
@emexelem
Copy link

emexelem commented Nov 7, 2018

Same issue here using v4.18:

[linux_eslint] ERROR: Parse error at line 35 column 10:
[linux_eslint] 
[linux_eslint] 29: $panelPosLeft: (xs: translateX(100%), lg: none);
[linux_eslint] 30: $panelLeft: (xs: -100%, lg: 0);
[linux_eslint] 31: $panelGlobalDimension: (xs: calc(100vh - 60px), lg: auto);
[linux_eslint] 32: $panelTransition: (xs: transform $timing0-3 ease, lg: none);
[linux_eslint] 33: 
[linux_eslint] 34: .navigation {
[linux_eslint] 35:   $root: &;
[linux_eslint]              ^

Can you please confirm if it's going to be fixed in v4.19, and when this version will be available?

Thanks

@emexelem
Copy link

I built #118 locally, it's working fine.

@dingo-d
Copy link
Author

dingo-d commented Nov 13, 2018

Let's hope it's merged to the plugin soon. :)

@racodond
Copy link
Owner

Hi,

The issue is indeed fixed.
As you can see in the builds, everything works fine for the LTS version (6.7), but not for the latest release (issue related to custom rules, nothing related to this issue). I just want to find some time to fix the issue related to the latest SonarQube version before releasing a version fixing this issue.

David

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

No branches or pull requests

3 participants