adrienverge / yamllint / 933

100%

push

travis-ci

Fix bug with CRLF in new-lines and require-starting-space

Pound-signs followed by a lone CRLF should not
raise if require-starting-space is specified.

If require-starting-space is true, *and* either:
- new-lines: disbale, or
- newlines: type: dos
is specified, a line with `#\r` or `#\r\n` should
not raise a false positive.

This commit also uses a Set for O(1) membership testing
and uses the correct escape sequence for the nul byte.

If we find a CRLF when looking for Unix newlines, yamllint
should always raise, regardless of logic with
require-starting-space.

Closes: Issue #171.

1 of 1 new or added line in 1 file covered. (100.0%)

1093 of 1116 relevant lines covered (97.94%)

5.86 hits per line