The Dart linter is a static analyzer for identifying possible problems in your Dart source code. More than a hundred linter rules are available, checking anything from potential typing issues, coding style, and formatting. This package,
lints, contains the lint settings recommended by the Dart team.
Two sets of lints are available:
Core lints: Lints that help identify critical issues that are likely to lead to problems when running or consuming Dart code. All code should pass these lints.
Recommended lints: Lints that help identify additional issues that may lead to problems when running or consuming Dart code, and lints that enforce writing Dart using a single, idiomatic style and format. All code is encouraged to pass these lints. The recommended lints include all the core lints.
When creating new Dart project using the
dart create command, the lints from
package:lints are enabled by default.
When uploading a package to the pub.dev package repository, packages are awarded pub points based on how many of the ‘core’ lints pass.
For documentation on the individual lints, see the linter rules page on dart.dev.
For new apps created with
dart create, the lints are enabled by default.
For existing apps or packages, take these steps to enable these lints:
In a terminal, located at the root of your package, run this command:
dart pub add --dev lints
Create a new
analysis_options.yaml file, next to the pubspec, that includes the lints package:
You can customize the predefined lint sets, both to disable one or more of the lints included, or to add additional lints. For details see customizing static analysis.
In migrating from the predefined lint sets provided by the
package:pedantic, you get static analysis coverage from 29 additional lints. There are, however, 6 lints which the pedantic package includes which are not included in the predefined lint sets provided by the lints package:
sort_child_properties_last (included in
use_full_hex_values_for_flutter_colors (included in
package:flutter_lints). To keep any of these lints enabled, add them to your analysis options.
The Dart language changes and the ecosystem continues to develop new best practices, so the lint sets must be periodically updated to reflect the best way we know to write Dart code. The informal process we use is:
Anyone can file an issue to discuss a potential change to a lint set. (A change here means adding or removing a lint from one or both sets. If you want to discuss implementing an entirely new lint, the place to suggest that is at the linter repo.) Feedback is welcome from any Dart user.
Periodically, a group of Dart and Flutter team members meet to review the suggestions and decide what to adopt.
The lists are updated and a new version of the package is published.