twbs / bootlint Goto Github PK

Refs twbs/bootstrap#13150

$ ./src/cli.js  
env: nodejs: No such file or directory

Haven't seen #!/usr/bin/env nodejs before, all I know of is #!/usr/bin/env node.

Valid structure is:

div.checkbox>label>input[type="checkbox"]
div.radio>label>input[type="radio"]
label.checkbox-inline>input[type="checkbox"]
label.radio-inline>input[type="radio"]

Because _FUCK JavaScript_, but this still needs to be able to run in-browser.

Need to exempt .row.show-grid and .row.responsive-utilities-test

Same for popovers too

Refs twbs/bootstrap#14252

Wrong:

    <div class="input-group">
        <span class="input-group-btn">
            <button id="button" class="btn btn-default btn-lg" type="button">Go!</button>
        </span>
        <input id="input" type="text" class="form-control input-lg" />
    </div>

Right:

    <div class="input-group input-group-lg">
        <span class="input-group-btn">
            <button id="button" class="btn btn-default" type="button">Go!</button>
        </span>
        <input id="input" type="text" class="form-control" />
    </div>

Refs twbs/bootstrap#14293
Checking for exactly 1 <button> child seems sufficient.

Selecting for the jQuery script can return a false positive warning if a user renames the jQuery file, such as when jQuery is concatenated with other JS.

Probably not going to be a common issue in the wild, but should be noted in the caveats maybe?

I guess http://www.bootstrapcdn.com/ , if they're willing.

Refs twbs/bootstrap#14230

Refs twbs/bootstrap#14300

Nesting should be used instead.
Need to verify this with @mdo.

If possible.

Pull requests welcome.

I still see this more often than I'd like to see it.

<div class=".container">
  <!-- Some other things -->
  <div class=".container">
    <!-- Things in nested container>
  </div>
</div>

Sometimes this might be desired, but more often than not it screws up the grid.

See: twbs/bootstrap#11436

Specifically, form groups and grid classes should not be combined with them; nesting should be used instead

The violations are:

• The Customizer page
• The gallery-ish "Downloads" and "Examples" sections of the Getting Started page
• The "Column sizing" example in the "Forms" section of the CSS page

Same for popovers too