2
100%
master: 100%

Ran 11 May 2015 02:03PM UTC

Files 12

Run time 2s

Badge

Embed ▾

Committed 10 May 2015 06:09PM UTC coverage: 96.561% (+0.03%) from 96.527%

Job # 1819.2

Build Type

push

travis-ci

Committed by

jugglinmike

Commit Message

[[FIX]] Allow lexer to communicate completion

Currently, JSHint's lexer continuously emits new "end-of-file" token
once all input has been consumed. This behavior makes the internal
`advance` function dangerous to use within iteration contexts. Such
usages need to explicitly check for the "end-of-file" token in order to
avoid entering non-terminating states.

Some of JSHint's parsing logic (such as that for template literal
parsing) takes this detail into account. Other areas (i.e. parsing class
bodies and function parameter lists) does not. While it would be
possible to extend each use with explicit safety checks, the possibility
for error in future feature additions would remain.

Update the lexer to consistently emit `null` after producing the
"end-of-file" token, alleviating the requirement of explicit safety
checks in `advance`-calling code. Update existing unit tests with the
new parsing error information (which is more accurate in many cases).

Run Details

3678 of 3809 relevant lines covered (96.56%)

2699.47 hits per line

jshint / jshint / 1819 / 2
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1819.2

jshint / jshint / 1819 / 2 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1819.2

jshint / jshint / 1819 / 2
100%
master: 100%

README BADGES
x