Skip to content

Include Flutter-specific lints or add another superset #229

Open
@parlough

Description

I'd really like to standardize all of my dart-lang and flutter org contributions to use this as a single analysis package, however that's difficult as Flutter apps often like to base their analysis on package:flutter_lints, which includes some helpful Flutter-specific lints. This results in a mix not only between repositories, but sometimes within the same repository.

Primary options:

  1. Base package:dart_flutter_team_lints on package:flutter_lints.

    • I'm not the biggest fan, mostly because it includes the avoid_print lint, but that can always be disabled :)
    • Technically will enable more lints even for Dart packages, potentially reducing analysis server performance, but should fail early.
  2. Create a new superset of package:dart_flutter_team_lints, perhaps at lib/flutter_analysis_options.yaml that adds its own set of Flutter specific lints on top.

A few projects that could benefit:

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions