Make syntax errors prevail over yamllint 'warnings'
When both a syntax error (unability to parse a document) and a cosmetic yamllint problem are found at the same place, the yamllint problem had the priority -- and the syntax error was not displayed. This had the following problem: if a rule is at the 'warning' level, its problems will not make the `yamllint` script return a failure return code (`!= 0`), even when it should (because there was a syntax error, precisely). This commit changes this behavior by preferring yamllint problems only when they have the 'error' level.pull/4/head
parent
97e2210ec9
commit
918f15b68d
Loading…
Reference in New Issue