• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

sds / scss-lint / 1160 / 1
96%
master: 96%

Build:
Build:
LAST BUILD BRANCH: patch-1
DEFAULT BRANCH: master
Ran 20 Feb 2016 03:55PM UTC
Files 89
Run time 4s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Feb 2016 03:52PM UTC coverage: 96.372% (-0.06%) from 96.43%
1.9.3

push

travis-ci

lencioni
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

2603 of 2701 relevant lines covered (96.37%)

368.65 hits per line

Source Files on job 1160.1 (1.9.3)
  • Tree
  • List 0
  • Changed 10
  • Source Changed 1
  • Coverage Changed 10
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1160
  • Travis Job 1160.1
  • 33ab4ef9 on github
  • Prev Job for 1.9.3 on PrivateNamingConvention (#1154.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc