5
96%
master: 96%

Ran 18 Feb 2016 09:35PM UTC

Files 89

Run time 24min

Badge

Embed ▾

Committed 18 Feb 2016 09:34PM UTC coverage: 96.39%. Remained the same

Job # 2.3.0

Build Type

push

travis-ci

Committed by

lencioni

Commit Message

Add PrivateNamingConvention linter

Although the `NameFormat` linter has an option to allow for leading
underscores, it does not enforce the convention. It would be really
great to either have a linter that does this.

What I mean by enforcing privacy for the leading underscore convention
is, for variables, functions, and mixins that start with a leading
underscore, we should verify that:

- any definitions are used within the same file
- any uses are defined within the same file
- any uses are preceded by their definitions

I considered adding this to `NameFormat`, but it seems specialized
enough that I decided to put it in its own linter. I left the prefix
configurable but defaulting to `_`, which is likely what most people
would use anyway.

Fixes #721

Coverage Stats

2590 of 2687 relevant lines covered (96.39%)

369.2 hits per line

sds / scss-lint / 1148 / 5
96%
master: 96%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1148.5 (2.3.0)

sds / scss-lint / 1148 / 5 96% master: 96%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1148.5 (2.3.0)

sds / scss-lint / 1148 / 5
96%
master: 96%

README BADGES
x