Files

T

Konstantin Shcheglov e67cd0daab The very first CL for end-to-end integration of FrontEnd resolution into Analysis Server.

At this point KernelDriver is used only by Analyzer, so I don't include
anyone from the FrontEnd team. We will merge to get the same performance
benefits of the latest IKG approach, but later.

Only just enought integration is done - we can store and apply
types in the local variable declaration.

Everything is in disarray, I will follow up with improvements.


R=brianwilkerson@google.com, paulberry@google.com

Bug:
Change-Id: Ie3434e26233b84fb019c50a7cc834a08d0dadbed
Reviewed-on: https://dart-review.googlesource.com/22202
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Paul Berry <paulberry@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>

2017-11-20 22:42:09 +00:00

bin

Add analytics to analyzer-cli and analysis server.

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

lib

Rename performace_logger.dart to performance_logger.dart

2017-11-03 20:24:00 +00:00

test

The very first CL for end-to-end integration of FrontEnd resolution into Analysis Server.

2017-11-20 22:42:09 +00:00

tool

Restore partial analysis of analysis options files

2017-06-22 08:00:50 -07: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

Cache PackageBundle instances in AnalyzerWorkerLoop and reuse for multiple requests.

2017-08-24 11:32:20 -07: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.