2
97%
default: 95%

Ran 20 Jun 2020 12:44AM UTC

Files 0

Run time 0s

Badge

Embed ▾

Committed 20 Jun 2020 12:28AM UTC coverage: 0.0%. First build

Job # 19.2

Build Type

push

travis-ci

Committed by

avnomad

Commit Message

Addressed an issue where the expected error message wouldn't be produced.

Before the fix, invalid expressions where a separator would appear just before
a terminator or end-of-input produced either an assertion error (if enabled) or
empty output. Instead a descriptive error message is now communicated to the
caller as an exception.

e.g. for an expression like "( ) ," you'll now get the message "A separator must
be followed by an operable expression!"

This was discovered while adding unit tests.

Also created a number of additional constants for error messages that
`parseInfixExpression` could produce and used them to replace the corresponding
string literals in the latter.

--HG--
branch : bugfix

Run Details

0 of 0 relevant lines covered (NaN%)

0.0 hits per line

avnomad / dop-parser / 19 / 2
97%
default: 95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 19.2

avnomad / dop-parser / 19 / 2 97% default: 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 19.2

avnomad / dop-parser / 19 / 2
97%
default: 95%

README BADGES
x