Make `strict-inference` and `strict-raw-types` report as `error` instead of `warning`

[flamychann]

I enabled strict type check as per the Flutter documentation in my codebase. However, I found out that not all of them reports as error.

analyzer:
  language:
    strict-casts: true
    strict-inference: true
    strict-raw-types: true

strict-casts will be reported as error, which is wanted behaviour.

However, strict-inference and strict-raw-types will only report as warning in flutter analyze.

Is there any way to make strict-inference and strict-raw-types report as error instead of warning ?

[dart-github-bot]

Summary: User wants strict-inference and strict-raw-types analyzer options to produce errors, not warnings, for consistent strict type checking. Currently, only strict-casts behaves as expected.

[flamychann]

good bot

[scheglov]

@srawlins

[srawlins]

I expect we're actually going to move in the other direction, and make these all lint rules.

@zhenhao-ola can you say how the error/warning distinction affects your workflow? Why do you want it one way vs the other?

[flamychann]

We use flutter analyze --no-fatal-infos --no-fatal-warnings so that errors triggered will fail the CI, whereas warnings will not fail the CI.

What I wanted to achieve is that, strict-inference and strict-raw-types can be customized to generate error/warning based on user choice.

[srawlins]

You can change the severity of the codes being reported like so: https://dart.dev/tools/analysis#changing-the-severity-of-rules

It won't be strict-inference, it will be the code that is reported in your CI when you enable strict-inference.

[flamychann]

gotcha