|author||David Morgan <email@example.com>||Thu Aug 23 16:57:36 2018 +0200|
|committer||David Morgan <firstname.lastname@example.org>||Thu Aug 23 16:59:34 2018 +0200|
This package serves three purposes:
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.
Here is how static analysis is used internally at Google:
TODOhint is a permanent exception.
The currently enabled lints are:
linter: rules: - avoid_empty_else - avoid_return_types_on_setters - avoid_types_as_parameter_names - control_flow_in_finally - no_duplicate_case_values - prefer_contains - prefer_equal_for_default_values - prefer_is_not_empty - recursive_getters - throw_in_finally - unrelated_type_equality_checks - use_rethrow_when_possible - valid_regexps
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. # empty_statements # Enforcing use of dartfmt is sufficient to make empty statements obvious. # Also, see linter issue #383 for discussion of false positives. # prefer_bool_in_asserts # Obsolete in Dart 2; bool is required in asserts. # prefer_final_locals # Does not reflect standard usage.
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.
Please file feature requests and bugs at the issue tracker.