Document dartanalyzer analysis options changes (#28928)

This commit is contained in:
Dan Rubel 2017-02-28 15:19:52 -08:00 committed by GitHub
parent 36cec1faef
commit bfb8e82c6e

View file

@ -16,6 +16,25 @@
characters to the console on Windows. Calls to `Stdout.add*()` behave as
before.
### Tool changes
* Analysis
* The `dartanalyzer` now follows the same rules as the analysis server to find an analysis options file,
stopping when an analysis options file is found:
* Search up the directory hierarchy looking for an analysis options file.
* If analyzing a project referencing the [Flutter](https://flutter.io/) package, then use the
[default Flutter analysis options](https://github.com/flutter/flutter/blob/master/packages/flutter/lib/analysis_options_user.yaml)
found in `package:flutter`.
* If in a Bazel workspace, then use the analysis options in `package:dart.analysis_options/default.yaml` if it exists.
* Use the default analysis options rules.
* In addition, specific to `dartanalyzer`:
* an analysis options file can be specified on the command line via `--options`
and that file will be used instead of searching for an analysis options file.
* any analysis option specified on the command line (e.g. `--strong` or `--no-strong`)
takes precedence over any corresponding value specified in the analysis options file.
## 1.22.0
### Language