habitrack/learning/demo-app/analysis_options.yaml
2024-08-26 00:34:20 +02:00

41 lines
1.8 KiB
YAML

# This file configures the analyzer, which statically analyzes Dart code to
# check for errors, warnings, and lints.
#
# The issues identified by the analyzer are surfaced in the UI of Dart-enabled
# IDEs (https://dart.dev/tools#ides-and-editors). The analyzer can also be
# invoked from the command line by running `flutter analyze`.
# The following line activates a set of recommended lints for Flutter apps,
# packages, and plugins designed to encourage good coding practices.
# include: package:flutter_lints/flutter.yaml
include: package:very_good_analysis/analysis_options.yaml
analyzer:
exclude:
- "**.g.dart"
- "**.freezed.dart"
errors:
invalid_annotation_target: ignore
linter:
# The lint rules applied to this project can be customized in the
# section below to disable rules from the `package:flutter_lints/flutter.yaml`
# included above or to enable additional rules. A list of all available lints
# and their documentation is published at
# https://dart-lang.github.io/linter/lints/index.html.
#
# Instead of disabling a lint rule for the entire project in the
# section below, it can also be suppressed for a single line of code
# or a specific dart file by using the `// ignore: name_of_lint` and
# `// ignore_for_file: name_of_lint` syntax on the line or in the file
# producing the lint.
rules:
# a must for libs, but within a small app it is ok to leave it to the end
# and document important stuff only
public_member_api_docs: false
# I prefere relative imports within the app
always_use_package_imports: false
# things that belong together are easyer to find
sort_pub_dependencies: false
# if you learn a new framework, I think it is better to use and see the types
omit_local_variable_types: false