dart-static-analysis
Analyzing and Linting Dart Code
Contents
- Configuring Analysis Options
- Managing Linter Rules
- Resolving Type Promotion Failures
- Workflow: Static Analysis Setup and Execution
- Workflow: Fixing Type Promotion
- Examples
Configuring Analysis Options
Control static analysis by placing an analysis_options.yaml file at the root of your package.
- Enforce Strict Type Checks: Always enable
strict-casts,strict-inference, andstrict-raw-typesin theanalyzersection to catch implicit dynamic casts and un-inferred types at compile time. - Configure Formatting: Define
dart formatrules within theformattersection (e.g.,page_widthandtrailing_commas). - Exclude Generated Code: Use the
excludekey to ignore generated files (e.g.,**/*.g.dart,**/*.freezed.dart) to prevent false positives.
Managing Linter Rules
More from dart-lang/skills
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
2.1Kdart-fix-runtime-errors
Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.
2.1Kdart-run-static-analysis
Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.
2.0Kdart-use-pattern-matching
Use switch expressions and pattern matching where appropriate
2.0Kdart-resolve-package-conflicts
Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.
2.0Kdart-collect-coverage
Collect coverage using the coverage packge and create an LCOV report
2.0K