Open sgrekhov opened 1 month ago
When I run your script through dart analyze --fatal-infos
, I get an exit code of 1. So the second part of this issue is not with the analyzer, but with the test runner. Please open a separate issue.
For the first part, it would be good to clarify what 'fatal' means, in our help text.
When I run your script through
dart analyze --fatal-infos
, I get an exit code of 1. So the second part of this issue is not with the analyzer, but with the test runner. Please open a separate issue.
It's not clear how
--fatal-infos
analyzer flag works. If to ask for a help we will see the following:My first intuitive understanding was that with this flag all
info
level messages should be turned intoerrors
. But, after some research with @eernstg it was found that this flag affects exit code only. If it is true and intended, please update the help message to reflect this fact.The second. I have the following test.
I would expect that test runner should report an error here (use of the deprecated varianle is an
info
-level issue, but with// SharedOptions=--fatal-infos
the test runner should report this test as a failing. But it doesn't (there is no actual test from below in co19 repositiry, it just my local sandbox).Please clarify how
--fatal-infos
is intended to work? Should the test runner report an error in some test contain--fatal-info
andinfo
-level issue?