dart-fix-static-analysis-errors

Run dart analyze to list all diagnostics, then run dart fix --apply to resolve automatically fixable issues. Address remaining errors manually using null safety operators, explicit casts, and type annotations, then re-run dart analyze until it reports no issues.

Use the ? suffix to declare nullable types, the ! operator to assert non-null values, late for delayed initialization, and required for mandatory named parameters. For type promotion, check local variables against null or use the is operator within a block.

Dart flow analysis only promotes local variables, not instance fields, because fields can change between the check and the use. Copy the field to a local variable first, check the local for null, and then use the promoted local variable.

Add strict-casts: true, strict-inference: true, and strict-raw-types: true under analyzer.language in analysis_options.yaml. These flags prevent implicit downcasts from dynamic, force explicit type inference, and require type arguments on generics.

Yes, use // ignore: diagnostic_name to suppress a diagnostic on a single line, or // ignore_for_file: diagnostic_name at the top of a file to suppress it throughout. You can also customize severity levels in analysis_options.yaml.