4 Commits

Author	SHA1	Message	Date
Brad Solomon	512fe17047	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.	2020-04-30 16:38:19 +02:00
Adrien Vergé	fec2c2fba7	fix(parser): Correctly handle DOS new lines in 'line' rules ... Do not consider the trailing `\r` of a line a part of it.	2019-04-09 16:48:00 +02:00
Adrien Vergé	6b5948c06b	Tests: Reorganize common and global tests	2016-02-01 16:56:32 +01:00
Adrien Vergé	350213b165	Initial commit	2016-01-14 10:46:14 +01:00