Paul Berry
3e195c913f
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 - https://dart-review.googlesource.com/c/sdk/+/440546 - https://dart-review.googlesource.com/c/sdk/+/442167 - https://dart-review.googlesource.com/c/sdk/+/443633 Change-Id: Ia7c7ce5e0ab0ac32d61d8a93319c363c6a6a6964 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/506321 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
21 lines
567 B
YAML
21 lines
567 B
YAML
include: package:lints/recommended.yaml
|
|
|
|
analyzer:
|
|
errors:
|
|
constant_identifier_names: ignore
|
|
non_constant_identifier_names: ignore
|
|
# Ignoring this for all developers means developers don't need to ignore
|
|
# TODOs in their IDE settings.
|
|
todo: ignore
|
|
# Existing violations (109)
|
|
unintended_html_in_doc_comment: ignore
|
|
|
|
linter:
|
|
rules:
|
|
- always_declare_return_types
|
|
- avoid_bool_literals_in_conditional_expressions
|
|
- no_literal_bool_comparisons
|
|
- omit_local_variable_types
|
|
- prefer_single_quotes
|
|
- unawaited_futures
|