Files

T

Kevin Millikin be30b62e3d Remove the Kernel type inference listener

We have decided to move to a different API for Fasta/Analyzer
integration, one that doesn't involve compiling to Kernel or observing
type inference.  The listener API will become broken, so let's just
remove it before that happens.

We lose the ability to trace type inference so let's restore that
ability next.  The analyzer's resolution storer is not used, but that
code has been left.  The resolution applier will no longer work
without the resolution storer, so those tests have been disabled.

Change-Id: If9ac5aba2d5de7788d8a65f7fa8410599e636d21
Reviewed-on: https://dart-review.googlesource.com/42400
Commit-Queue: Kevin Millikin <kmillikin@google.com>
Reviewed-by: Paul Berry <paulberry@google.com>
Reviewed-by: Peter von der Ahé <ahe@google.com>

2018-02-21 16:28:07 +00:00

bin

Add analytics to analyzer-cli and analysis server.

2017-07-05 23:29:46 -07:00

lib

Revert "In CLI no batch, support analyzing multiple files in multiple contexts"

2018-02-20 23:08:41 +00:00

test

Remove the Kernel type inference listener

2018-02-21 16:28:07 +00:00

tool

Reland: [dart:cli] Adds waitFor(Future)

2018-01-18 16:38:54 +00:00

.gitignore

Add intellij metadata to the repo.

2017-02-10 12:47:06 -08:00

analysis_options.yaml

Add analytics to analyzer-cli and analysis server.

2017-07-05 23:29:46 -07:00

CHANGELOG.md

analyzer_cli move to SDK.

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

pubspec.yaml

Bumping protobuf version to ^0.7.0

2018-02-14 19:28:23 +00:00

README.md

Remove and hide analyzer cli flags.

2017-02-22 14:09:41 -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:

--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.