XO’s zero-config philosophy works great, but treating warnings as errors currently requires manually redefining every rule from warn to error in a local config. That approach is brittle, is prone to falling behind updates to XO configs (and their many warning-level rules), and goes against the zero-config philosophy in general. I’m filing this issue after noticing this has been a recurring pattern in my codebase.
A --strict config flag could solve this by treating all warnings as errors. No changes to the output—just the exit status.
If there’s consensus around adding this feature, I’d be happy to submit a PR.
XO’s zero-config philosophy works great, but treating warnings as errors currently requires manually redefining every rule from
warntoerrorin a local config. That approach is brittle, is prone to falling behind updates to XO configs (and their many warning-level rules), and goes against the zero-config philosophy in general. I’m filing this issue after noticing this has been a recurring pattern in my codebase.A
--strictconfig flag could solve this by treating all warnings as errors. No changes to the output—just the exit status.If there’s consensus around adding this feature, I’d be happy to submit a PR.