Hi!
I'm currently exploring Oxlint and I'm really impressed with the performance and the "Correctness-focused defaults" philosophy. However, I found a point of ambiguity that might be worth clarifying in the documentation.
While testing it on my project, I noticed that these default correctness rules are treated as warnings. This was a bit unexpected because, for a tool designed for CI and "high-signal" checks, one might expect these critical issues to be errors that fail the build by default.
Would it make sense to explicitly state in the "Quickstart" or "Rules reference" sections:
What is the default severity (Warning vs. Error) for these default/enabled rules?
Hi!
I'm currently exploring Oxlint and I'm really impressed with the performance and the "Correctness-focused defaults" philosophy. However, I found a point of ambiguity that might be worth clarifying in the documentation.
While testing it on my project, I noticed that these default correctness rules are treated as warnings. This was a bit unexpected because, for a tool designed for CI and "high-signal" checks, one might expect these critical issues to be errors that fail the build by default.
Would it make sense to explicitly state in the "Quickstart" or "Rules reference" sections:
What is the default severity (Warning vs. Error) for these default/enabled rules?