Paul Berry
9d82a86cd7
Some time ago, the analyzer team decided to adopt the convention of using `TODO` comments to document long term issues that should persist in the codebase, and `FIXME` comments to document short term issues that need immediate attention. Accordingly, it makes sense to suppress `TODO` comments from being surfaced to the IDE "problems" view (since there can be a lot of them, and they're not immediately actionable). This makes VSCode's "problems" view much more usable in "tree" mode. Previous CLs that have made this change in other packages: - https://dart-review.googlesource.com/c/sdk/+/295662 - https://dart-review.googlesource.com/c/sdk/+/325121 - https://dart-review.googlesource.com/c/sdk/+/358980 - https://dart-review.googlesource.com/c/sdk/+/410060 Change-Id: Icaa7351b57873f1015014792741ea919ecdf55e6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/440546 Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Auto-Submit: Paul Berry <paulberry@google.com>
29 lines
667 B
YAML
29 lines
667 B
YAML
include: package:lints/recommended.yaml
|
|
|
|
analyzer:
|
|
exclude:
|
|
- lib/mock_packages/package_content/**
|
|
errors:
|
|
# Ignoring this for all developers means developers don't need to ignore
|
|
# TODOs in their IDE settings.
|
|
todo: ignore
|
|
|
|
language:
|
|
strict-casts: true
|
|
strict-inference: true
|
|
strict-raw-types: true
|
|
|
|
linter:
|
|
rules:
|
|
- avoid_dynamic_calls
|
|
- avoid_unused_constructor_parameters
|
|
- flutter_style_todos
|
|
- library_annotations
|
|
- prefer_single_quotes
|
|
- unawaited_futures
|
|
- unnecessary_breaks
|
|
- unnecessary_ignore
|
|
- unnecessary_library_directive
|
|
- unnecessary_parenthesis
|
|
- unreachable_from_main
|