Use case
This originally came up at Dart-Code/Dart-Code#6073. Using Flutterfire with Swift Package Manager results in Dart files in the build/ folder which the analysis server analyzes, producing (potentially large numbers of) spurious analysis errors.
It doesn't make sense to analyze things in the build/ folder, but since this is a Flutter detail, it probably also does not make sense to code the exclusion into the analysis server.
Proposal
Include exclusions for any folders that Flutter creates that aren't expected to contain user-owned Dart files as exclusions in analysis_options.yaml for the flutter create templates:
analyzer:
exclude:
- build/
Use case
This originally came up at Dart-Code/Dart-Code#6073. Using Flutterfire with Swift Package Manager results in Dart files in the
build/folder which the analysis server analyzes, producing (potentially large numbers of) spurious analysis errors.It doesn't make sense to analyze things in the
build/folder, but since this is a Flutter detail, it probably also does not make sense to code the exclusion into the analysis server.Proposal
Include exclusions for any folders that Flutter creates that aren't expected to contain user-owned Dart files as exclusions in
analysis_options.yamlfor theflutter createtemplates: