Getting errors from imports without specifying the imports

[jgable]

Getting errors from imports without specifying the imports

[jgable]

Do you have a repo I can clone down and take a look at to confirm? If not,
would you mind creating a simple one so I don't chase the wrong thing down?

[dontwork]

I will be able to get you a repo in a day or 2. All I'm doing is linting an
less file which has imports. The grunt task then shows the 'rollup' errors
in terminal. If I do not include the bootstrap import it does not have the
errors so they are definitely caused by the bootstrap.less file being
imported.

Cheers. Great plugin apart from this minor issue!
On 30 Jan 2015 17:00, "Jacob Gable" [email protected] wrote:

Do you have a repo I can clone down and take a look at to confirm? If not,
would you mind creating a simple one so I don't chase the wrong thing
down?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[dontwork]

https://github.com/dontwork/lessLintTestRepo

There we go, same errors as before in this test repo!

[jgable]

Those are what are called "rollup" errors. They aren't necessarily specific to a certain file, but the whole aggregate of the generated stylesheet.

{ type: 'warning',
  rollup: true,
  message: 'Too many !important declarations (63), try to use less than 10 to avoid specificity issues.',
  rule: 
   { id: 'important',
     name: 'Disallow !important',
     desc: 'Be careful when using !important declaration',
     browsers: 'All',
     init: [Function] } }

There is no filename associated with the error so we have no way of telling whether it's in an import file or not. I started showing these with PR #34 since we were just silently ignoring them before.

You can ignore the errors explicitly by adding a csslint option

lesslint: {
  src: ['less/style.less'],
  options: {
    csslint: {
      important: false,
      "font-sizes": false,
      floats: false,
      "unique-headings": false
    }
  }
}

I see a couple options from here that this task could do, but I'm hesitant to jump right in on either:

1. Ignore rollup warnings in this task (they are just warnings after all)
2. Add a config option to treat these as errors optionally (combined with 1)

I'm going to close for now, since this isn't something we will be fixing for the time being.

[dontwork]

If I ignore those lint warnings won't it then ignore those warnings in my own style sheets? I wouldn't want that. Is there a setting to ignore the 'rollup' warnings and have them not appear. For this task to pass in a build I would have to permanently run it with force.

[jgable]

I looked for something on the CSS lint site that would disable rollups, but I could not find it. Ignoring rollups should be something that they support upstream and we pass to them as options.

If they are adamant about not providing a way to ignore rollups, then I'll consider ignoring and erroring behind a config option.

[dontwork]

Just to confirm then, the only option is to ignore the warnings from the bootstrap.less import at the expense of not seeing them for my own style sheets?