pedantic 1.5.0

pedantic #

This package serves three purposes:

  • It documents how Dart static analysis is used internally at Google, including best practices for the code we write. The documentation is this
  • It contains a corresponding sample analysis_options.yaml.
  • It contains occasional small snippets of Dart code that are used in implementing those best practices.

Note that everything here fits within the guidelines set out in Effective Dart. You could think of that document as the design and this package as one possible partial implementation.

Using Static Analysis #

Here is how static analysis is used internally at Google:

  • By default we disallow checking in code with any errors, warnings, or hints.
    • The TODO hint is a permanent exception.
    • Deprecation hints are a permanent exception. Deprecations are handled separately on a case by case basis.
    • unnecessary_no_such_method, unused_element, unused_field and unused_local_variable are allowed.
    • When a new SDK version adds new errors, warnings or hints, we either clean up everything before switching SDK version or maintain a whitelist of allowed violations so it can be gradually cleaned up.
  • Lints are considered and enabled on a case by case basis. When enabling a lint we first clean up all pre-existing violations. After it's enabled, any attempt to check in a further violation will be blocked.

Enabled Lints #

The currently enabled lints can be found in the sample analysis_options.yaml.

To use those lints you can add a dependency in your pubspec.yaml:

# If you also need to import `package:pedantic/pedantic.dart`, it's a
# normal dependency.
  pedantic: '1.4.0'

# Or, if you just want `analysis_options.yaml`, it can be a dev dependency.
  pedantic: '1.4.0'

and add an include in your analysis_options.yaml:

include: package:pedantic/analysis_options.yaml

This example uses a pinned version because every added lint rule could break a build for projects using it.

Unused Lints #

The following lints have been considered and will not be enforced:

always_put_control_body_on_new_line violates Effective Dart "DO format your code using dartfmt". See note about Flutter SDK style below.

always_specify_types violates Effective Dart "AVOID type annotating initialized local variables" and others. See note about Flutter SDK style below.

avoid_as does not reflect standard usage. See note about Flutter SDK style below.

control_flow_in_finally does not offer enough value: people are unlikely to do this by accident, and there are occasional valid uses.

empty_statements is superfluous, enforcing use of dartfmt is sufficient to make empty statements obvious.

prefer_bool_in_asserts is obsolete in Dart 2; bool is required in asserts.

prefer_final_locals does not reflect standard usage.

throw_in_finally does not offer enough value: people are unlikely to do this by accident, and there are occasional valid uses.

Note on Flutter SDK Style: some lints were created specifically to support Flutter SDK development. Flutter app developers should instead use standard Dart style as described in Effective Dart, and should not use these lints.

Features and bugs #

Please file feature requests and bugs at the issue tracker.

1.5.0 #

1.4.0 #

  • Enforce avoid_init_to_null and null_closures.

1.3.0 #

  • Enforce prefer_is_empty.

1.2.0 #

  • Enforce unawaited_futures. Stop enforcing control_flow_in_finally and throw_in_finally.

1.1.0 #

  • Move analysis_options.yaml under lib so you can import it directly from your own analysis_options.yaml. See for example.

1.0.0 #

  • Describe Dart static analysis use at Google in
  • Add sample analysis_options.yaml.
  • Add unawaited method for silencing the unawaited_futures lint.

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:

  pedantic: ^1.5.0

2. Install it

You can install packages from the command line:

with pub:

$ pub get

with Flutter:

$ flutter pub get

Alternatively, your editor might support pub get or flutter pub get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:

import 'package:pedantic/pedantic.dart';
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
Learn more about scoring.

We analyzed this package on Jan 29, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.7.1
  • pana: 0.13.4

Maintenance suggestions

Maintain an example. (-10 points)

Create a short demo in the example/ directory to show how to use this package.

Common filename patterns include main.dart, example.dart, and pedantic.dart. Packages with multiple examples should provide example/

For more information see the pub package layout conventions.

The package description is too short. (-8 points)

Add more detail to the description field of pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.


Package Constraint Resolved Available
Direct dependencies
Dart SDK >=2.1.1-dev.0.0 <3.0.0