core_analysis

Description:

core analysis

analysis_options for core projects.
Usage #
To use the lints, add as a dev dependency in your pubspec.yaml:
dart pub add dev:core_analysis
# or
flutter pub add dev:core_analysis
copied to clipboard
Then, add an include in analysis_options.yaml:
include: package:core_analysis/analysis_options_dev.yaml
# use analysis_options.yaml for production-readyness
# include: package:core_analysis/analysis_options.yaml
copied to clipboard
This will ensure you always use the latest version of the lints. If you wish to restrict the lint version, specify a version of analysis_options.yaml instead:
include: package:core_analysis/analysis_options.0.1.0.yaml
copied to clipboard
Suppressing Lints #
There may be cases where specific lint rules are undesirable. Lint rules can be suppressed at the line, file, or project level.
An example use case for suppressing lint rules at the file level is suppressing the prefer_const_constructors in order to achieve 100% code coverage. This is due to the fact that const constructors are executed before the tests are run, resulting in no coverage collection.
Line Level #
To suppress a specific lint rule for a specific line of code, use an ignore comment directly above the line:
// ignore: public_member_api_docs
class A {}
copied to clipboard
File Level #
To suppress a specific lint rule of a specific file, use an ignore_for_file comment at the top of the file:
// ignore_for_file: public_member_api_docs

class A {}

class B {}
copied to clipboard
Project Level #
To suppress a specific lint rule for an entire project, modify analysis_options.yaml:
include: package:core_analysis/analysis_options.yaml
linter:
rules:
public_member_api_docs: false
copied to clipboard