625
100%

Ran 18 Nov 2015 09:47PM UTC

Jobs 1

Files 49

Run time 10s

Badge

Embed ▾

pending completion

Build # 625

Build Type

Pull #319

travis-ci

Committed by

tofumatt

Commit Message

Import and define rules directly (fix #317)

We can define the ESLint rules directly using the `ESLint.linter.defineRule`
API and using `ESLint.linter.verify()` method to scan each file.

This means we _do_, unfortunately, need to explicitly enable ES6 features in
the ecmafeatures property as there isn't an easy "env" setting that I'm aware
of. Maybe there is and I didn't find it; at any rate this allows our code
coverage tools to scan our rules (it caught one skipped test!) and simplifies
our build process a lot.

Pull Request Pull Request #319: Import and define rules directly (fix #317)

Run Details

760 of 760 relevant lines covered (100.0%)

86.07 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	625.1	18 Nov 2015 09:47PM UTC	0	100.0	Travis Job 625.1

Source Files on build 625

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

mozilla / addons-linter / 625
100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 625

mozilla / addons-linter / 625 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 625

mozilla / addons-linter / 625
100%

README BADGES
x