2
72%
master: 63%

Ran 22 Dec 2019 06:02AM UTC

Files 8

Run time 0s

Badge

Embed ▾

Committed 22 Dec 2019 06:01AM UTC coverage: 72.206% (+1.1%) from 71.116%

Job # 1068.2

Build Type

push

travis-ci-com

Committed by

odino

Commit Message

Use a more flexible structure for the spec argument to validateVarArgs (#309)

* Use a more flexible structure for the spec argument to validateVarArgs

validateVarArgs' argument specification now uses a format that supports
multiple argument signatures, each of whose arguments are in turn a list
of supported types. For example, to achieve:

  foo(string, [string|number])
  foo(string)

Your argument would be:

  {
    {{STRING_OBJ}, {STRING_OBJ, NUMBER_OBJ}},
    {{STRING_OBJ}},
  }

Matching is done in order, giving priority to specs by lower index.

Additionally, validateVarArgs is now smart enough to figure out the
minimum and maximum number of arguments on its own.

When validateVarArgs fails to match a spec, it will return an error with
a usage string showing the alternate calling signatures. On success, it
will return the index of the matched signature as the second return
value.

* arr.join() now defaults to an empty string as glue when no argument is specfied

* validateVarArgs' error message should begin with 'Usage:'

* Remove debug line

* split() defaults to a single space

* Update docs for join(), split()

Run Details

2972 of 4116 relevant lines covered (72.21%)

46.48 hits per line

abs-lang / abs / 1068 / 2
72%
master: 63%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1068.2

abs-lang / abs / 1068 / 2 72% master: 63%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1068.2

abs-lang / abs / 1068 / 2
72%
master: 63%

README BADGES
x