Open aaronmallen opened 1 month ago
My current work around:
# Steepfile
configure_code_diagnostics do |config|
config[Steep::Diagnostic::Ruby::BlockTypeMismatch] = :hint
end
It exits with error when it prints diagnostics. So, passing --severity-level
to steep check
would be another workaround.
I don't think giving Error
diagnostics a special treatment is a good way. Adding a command line option like --fail-severity-level=error
?
The convention is that exit status 0 means success. Warning is not a failure. Compilers have an option to treat warnings as errors, I suggest following the same logic with steep: add an option to exit with 1 if any warnings are emitted, by default warnings should exit with 0.
Currently steep will exit with code
1
on warning: