Files

T

Paul Berry ea189bd6dc Add a fallback mode for building summaries.

When summaries are built in fallback mode, the only information stored
in the package bundle is (a) which libraries appear in the bundle, and
(b) where the source files can be found on disk.  This is enough
information so that DDC will still be able to tell how libraries are
grouped into build units, but otherwise summary functionality is
disabled.

This is intended to be availadle as a temporary workaround so that if
a bug is found in the summary infrastructure, it won't prevent DDC
compilation from working (it will just make it slower).

R=scheglov@google.com

Review URL: https://codereview.chromium.org/1826353002 .

2016-03-24 13:47:37 -07:00

bin

Add hook to command-line analyzer similar to server

2016-01-29 13:31:25 -08:00

lib

Add a fallback mode for building summaries.

2016-03-24 13:47:37 -07:00

test

Add a fallback mode for building summaries.

2016-03-24 13:47:37 -07:00

.analysis_options

Suppress warnings in analyzer_cli test data

2016-03-17 13:01:12 -07:00

.gitignore

analyzer_cli move to SDK.

2015-11-19 14:52:54 -08:00

CHANGELOG.md

analyzer_cli move to SDK.

2015-11-19 14:52:54 -08:00

pubspec.yaml

Initial hermetic package analyzer.

2016-02-22 17:19:27 -08:00

README.md

CLI doc update to remove contributor bits.

2015-12-08 12:40:34 -08:00

README.md

dartanalyzer

Use dartanalyzer to statically analyze your code at the command line, checking for errors and warnings that are specified in the Dart Language Specification. DartPad, code editors, and IDEs such as WebStorm use the same analysis engine that dartanalyzer uses.

Basic usage

Run the analyzer from the top directory of the package. Here's an example of testing a Dart file.

dartanalyzer bin/test.dart

Options

The following are the most commonly used options for dartanalyzer:

--packages=
Specify the path to the package resolution configuration file. For more information see Package Resolution Configuration File. This option cannot be used with --package-root.
--package-warnings
Show warnings not only for code in the specified .dart file and others in its library, but also for libraries imported with package:.
--options=
Specify the path to an analysis options file.
--lints
Show the results from the linter.
--no-hints
Don't show hints for improving the code.
--ignore-unrecognized-flags
Rather than printing the help message, ignore any unrecognized command-line flags.
--version
Show the analyzer version.
-h or --help
Show all the command-line options.

The following are advanced options to use with dartanalyzer:

-b or --batch
Run in batch mode.
--dart-sdk=
Specify the directory that contains the Dart SDK.
--fatal-warnings
Except for type warnings, treat warnings as fatal.
--format=machine
Produce output in a format suitable for parsing.
--url-mapping=libraryUri,/path/to/library.dart
Tells the analyzer to use the specified library as the source for that particular import.

The following options are deprecated:

-p or --package-root=
Deprecated. Specify the directory to search for any libraries that are imported using package:. This option is replaced as of Dart 1.12 with --packages.
--machine
Deprecated. Replaced by --format.
--show-package-warnings
Deprecated. Replaced by --package-warnings.
--show-sdk-warnings
Deprecated. Replaced by --warnings.