Mixin parsing error

[davegreenwp]

I've just started using sass-lint via grunt-sass-lint and I'm getting a parsing error due to this mixin that I have:

/// Input placeholder styling
/// @param {List} $styles - Styles
/// @requires $kp-ph--prefixes
/// @group forms
@mixin kp-placeholder-styles($styles) {
  @each $pseudo in $kp-ph--prefixes {
    @at-root &#{$pseudo} {

      @each $key, $value in $styles {
        #{$key}: #{$value};
      }
    }

    @at-root &:focus#{$pseudo} {
      color: transparent;
    }
  }
}

Producing this error:

I've quickly copied the mixin and variables it depends on into Sassmeister (using Libsass 3.2.5 option) and it's working perfectly. I know this code is producing the correct results as I'm using it in a number of projects.

I was wondering whether this could be related to #44 but felt it best to post a new issue in case.

[davegreenwp]

After a little testing it seems that it doesn't like more than one interpolated string per line?

EDIT: I commented out the offending code posted above to see what the next error would be, and it's failed when parsing a Bootstrap include which has several interpolated strings on the same line as follows:

  src: url(if($bootstrap-sass-asset-helper, twbs-font-path('#{$icon-font-path}#{$icon-font-name}.eot'), '#{$icon-font-path}#{$icon-font-name}.eot'));

[DanPurdy]

Hmm, this looks like another issue with our AST, gonzales-pe.. I'm afraid we may be a little restricted in what we can do to fix this.. Will double check later on though...

[Undistraction]

FWIW this seems to fail on any interpolated value, quoted or otherwise, for example:

@mixin example {
    $name: 'width';
    #{$name}: 100%;
}

[DanPurdy]

Yeah @Undistraction we are just waiting for the latest release of our AST to happen, it should fix the problems with interpolated strings. Looks like under a week now. Fingers crossed!

[Undistraction]

@DanPurdy That's great news. Thanks for the headsup.

[DanPurdy]

See here for more info #222

[davegreenwp]

@DanPurdy That's excellent news! Looking forward to kicking grunt-scss-lint out of bed once it drops! 👍

[aarr0n]

👍

[DanPurdy]

The original issue above is still causing a parse error as of the latest build of gonzales-pe (3.2.1) I've filed it as a fresh issue to hopefully see this fixed. You can follow the issue here

[davegreenwp]

@DanPurdy Thanks for the update, much appreciated

[davegreenwp]

@DanPurdy now that the issue is fixed in gonzales-3.2.x, are we just waiting for a sass-lint update which includes that update?

[DanPurdy]

Yes, unfortunately gonzales-pe isn't installing on windows at moment due to some bash specific post install scripts so we're waiting for them to update or if we'll just fork it and roll our own version of it soon. Fingers crossed it wont be too long!

[DanPurdy]

@davetgreen This is fixed in sass-lint 1.6.0

[davegreenwp]

@DanPurdy Thank you so much!