-
Notifications
You must be signed in to change notification settings - Fork 3
/
analysis_options.yaml
57 lines (46 loc) · 2.04 KB
/
analysis_options.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
include: all_lint_rules.yaml
analyzer:
exclude:
- "**/*.g.dart"
strong-mode:
implicit-casts: false
implicit-dynamic: false
errors:
# Otherwise cause the import of all_lint_rules to warn because of some rules conflicts.
# We explicitly enabled even conflicting rules and are fixing the conflict
# in this file
included_file_warning: ignore
# false positive when using Freezed
invalid_annotation_target: ignore
linter:
rules:
# False positive for custom enum-like classes (such as Flutter's "Colors")
avoid_classes_with_only_static_members: false
# Not needed right now, maybe re-activate it later
flutter_style_todos: false
# false positive
one_member_abstracts: false
# Too verbose with little value, and this is taken care of by the Flutter devtool anyway.
diagnostic_describe_all_properties: false
# Conflicts with `avoid_final_parameters`
prefer_final_parameters: false
# Conflicts with `prefer_single_quotes`
# Single quotes are easier to type and don't compromise on readability.
prefer_double_quotes: false
# Conflicts with `omit_local_variable_types` and other rules.
# As per Dart guidelines, we want to avoid unnecessary types to make the code
# more readable.
# See https://dart.dev/guides/language/effective-dart/design#avoid-type-annotating-initialized-local-variables
always_specify_types: false
# There are situations where we voluntarily want to catch everything,
# especially as a library.
avoid_catches_without_on_clauses: false
# Incompatible with `prefer_final_locals`
# Having immutable local variables makes larger functions more predictable
# so we will use `prefer_final_locals` instead.
unnecessary_final: false
# Not quite suitable for Flutter, which may have a `build` method with a single
# return, but that return is still complex enough that a "body" is worth it.
prefer_expression_function_bodies: false
# conflicts with `prefer_relative_imports`
always_use_package_imports: false