sds / scss-lint

96%

master: 96%

LAST BUILD ON BRANCH PrivateNamingConvention

branch: PrivateNamingConvention

CHANGE BRANCH

x

Reset

• PrivateNamingConvention
• master
• v0.40.0
• v0.40.1
• v0.41.0
• v0.42.0
• trailing-semicolon-important
• bang-format
• v0.42.1
• v0.42.2
• v0.43.0
• pseudoselector
• v0.43.1
• v0.43.2
• v0.44.0
• universal-newline
• single-line-per-property-nesting
• relax-rake-dependency-version
• v0.45.0
• linter-gem-spec
• tap-reporter
• private-naming-edge-cases
• v0.46.0
• private-naming-convention-bugs
• tap-reporter-format
• v0.47.0
• tap-report-path-fix
• v0.47.1
• v0.48.0
• v0.49.0
• v0.50.0
• v0.50.1
• v0.50.2
• v0.50.3
• v0.51.0
• v0.52.0
• v0.53.0
• v0.54.0
• v0.55.0
• v0.56.0
• v0.57.0
• v0.57.1
• v0.58.0
• v0.59.0

Build # 1160

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

Run Details

2742 of 2850 relevant lines covered (96.21%)

1767.33 hits per line