languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-16 03:47:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/pkg/analyzer_cli
History
Konstantin Shcheglov 149ebf683b Support for 'uri' property of Import/Export/CompilationUnitElement. 
_Builder in source_gen uses code like this to check that the generated
file is expected in the library. While it is a questionable approach,
I don't feel that I have time to fix it, and remove the `uri` property
completely. So, we fix in in Analyzer with summary2.

`if (!library.parts.map((c) => c.uri).contains(part)) { ...fail... }`

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

Change-Id: I983f29589cbb2613d5f896b87f6218c31a47afa9
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/105601
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
2019-06-11 16:53:03 +00:00
..
bin Finish cleaning up the copyright notices in the analyzer_cli package 2019-01-06 19:16:31 +00:00
lib Support for 'uri' property of Import/Export/CompilationUnitElement. 2019-06-11 16:53:03 +00:00
test Prepare to compute the documentation URL for diagnostics 2019-06-06 16:41:46 +00:00
tool Add featureSet parameter to Parser constructor. 2019-04-29 16:42:19 +00:00
.gitignore Add intellij metadata to the repo. 2017-02-10 12:47:06 -08:00
analysis_options.yaml Try no implicit casts in pkg/analyzer_cli. 2018-08-08 22:14:12 +00:00
CHANGELOG.md analyzer_cli move to SDK. 2015-11-19 14:52:54 -08:00
pubspec.yaml Remove usages of ExtensionManager and package:plugin in general. 2019-03-14 15:31:08 +00:00
README.md modernize IDE reference 2018-10-25 14:19:31 +00: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 Android Studio and VS Code 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.