twbs / grunt-bootlint Goto Github PK

/CC @zacechola @cvrebert

I miss the option to disable one or more Lint Problem IDs (https://github.com/twbs/bootlint/wiki/)

See discussion: https://github.com/XhmikosR/grunt-bootlint/commit/8a82a2f564dfd8be3b9cf64c3da4548295661ca2

Refs #31 (comments)

And maybe update any other deps along the way too.

By which I mean, set https://www.npmjs.org/package/grunt-bootlint in the field next to the "Grunt wrapper for bootlint" description field at the top of the repo homepage

twbs/bootlint#44 fixed this, so no more long require.

Features

#35 add stoponwarning option

See discussion: https://github.com/XhmikosR/grunt-bootlint/commit/8a82a2f564dfd8be3b9cf64c3da4548295661ca2

Use grunt.log colors instead.

See: twbs/bootlint#30

I'm trying to lint a php page generated by WordPress, with the following code:

bootlint: {  
    options: {  
        stoponerror: false,
        relaxerror: []
    },
    files: ["http://local.dev/"],
    }

I'm removing the doctype from the document at that URL so that it should trigger a Bootlint error, but all I get is "no Bootlint errors" so I don't believe that the page is actually getting scanned. When I point at a sample page that's mapped via the file system (i.e. files: ["path/file.php"]) then Bootlint does trigger errors as expected.

Since I'm using a CMS only linting the rendered pages make sense. (Sorry for having misfiled this earlier under the main bootlint project instead of here, and thanks for doing this!)

See https://github.com/twbs/bootlint/releases/tag/v0.14.1

syntax issues in the usage section.

😡

Could you tweak the description in package.json so that it mentions grunt?
Right now the description is exactly the same as that of Bootlint itself (except for "An "), which is slightly confusing.

/CC @cvrebert @zacechola

It will be nice to be able to list for which files should be ID in relaxerror disabled.

Provide option to stop linting on first error found.

Add more granular controls for task failure on (non-relaxed) warnings and errors.

For example:

• (stoponerror && stoponwarning == false): Only fail the task on errors.
• (stoponerror && stoponwarning): Fail the task on any error or warning.

This is sort of breaking behavior for stoponerror.

🚢

v0.6.0 is on npm, but it's not on https://github.com/zacechola/grunt-bootlint/releases

Refs #37

<div class="row">
  <div class="col-xs-11"></div>
  <% if (condition) { %>
    <div class="col-xs-1"></div>
  <% } %>
</div>

This code raises errors E013 and E014 and I don't want to relax those errors on the entire project.
Is it possible to have bootlint ignore templating code?

Refs twbs/bootlint#172

Refs: twbs/bootlint#103

Right now it logs out the error as a warning, but doesn't cause a failure.

Might want to make that an option to toggle on or off.

Refs: twbs/bootlint/issues/68