Crispy Analysis

Maintained by Riccardo Strazzer

---

This package provides lint rules for Dart and Flutter which are used at Crispy Bacon SRL. For more information, see the complete list of options.

The example folder contains some example. If you find some cases where some rules are too aggressive please fill a issue and we can discuss about it's removal.

Usage

To use the lints, add as a dev dependency in your pubspec.yaml:

crispy_analysis:
  git: https://github.com/crispybaconsrl/crispy_analysis

Then, add an include in analysis_options.yaml:

include: package:crispy_analysis/analysis_options.yaml

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:crispy_analysis/analysis_options.1.0.2.yaml

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 {}

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 {}

Project Level

To suppress a specific lint rule for an entire project, modify analysis_options.yaml:

include: package:crispy_analysis/analysis_options.yaml
linter:
  rules:
    public_member_api_docs: false

Badge

To indicate your project is using crispy_analysis →

[![style: crispy analysis](https://img.shields.io/badge/style-crispy_analysis-A1022B.svg)](https://github.com/crispybaconsrl/crispy_analysis)