667
98%
master: 100%

Ran 09 Jan 2019 09:05PM UTC

Jobs 6

Files 29

Run time 6min

Badge

Embed ▾

pending completion

Build # 667

Build Type

push

travis-ci

Committed by

adrienverge

Commit Message

config: Do not require all rule options to be set

Before, it was required to specify all the options when customizing a
rule. For instance, one could use `empty-lines: enable` or `empty-lines:
{max: 1, max-start: 2, max-end: 2}`, but not just `empty-lines: {max:
1}` (it would fail with *invalid config: missing option "max-start" for
rule "empty-lines"*).

This was a minor problem for users, but it prevented the addition of new
options to existing rules, see [1] for an example. If a new option was
added, updating yamllint for all users that customize the rule would
produce a crash (*invalid config: missing option ...*).

To avoid that, let's embed default values inside the rules themselves,
instead of keeping them in `conf/default.yaml`.

[1]: https://github.com/adrienverge/yamllint/pull/151

Run Details

991 of 1008 relevant lines covered (98.31%)

5.87 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	667.1	09 Jan 2019 09:10PM UTC	98.31	Travis Job 667.1
2	667.2	09 Jan 2019 09:05PM UTC	97.92	Travis Job 667.2
3	667.3	09 Jan 2019 09:06PM UTC	97.92	Travis Job 667.3
4	667.4	09 Jan 2019 09:05PM UTC	97.92	Travis Job 667.4
5	667.5	09 Jan 2019 09:05PM UTC	97.92	Travis Job 667.5
6	667.6	09 Jan 2019 09:12PM UTC	97.92	Travis Job 667.6

Source Files on build 667

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

adrienverge / yamllint / 667
98%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 667

adrienverge / yamllint / 667 98% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 667

adrienverge / yamllint / 667
98%
master: 100%

README BADGES
x