mirror of https://github.com/dart-lang/sdk synced 2024-11-02 12:24:24 +00:00

History

Vijay Menon b8d3758dcd Revert "Transition analyzer and analysis_server to new astFactory; remove old AST factory methods." This reverts commit `1d028eed8d`. This was breaking DDC. TBR=paulberry@google.com Review URL: https://codereview.chromium.org/2542753002 .		2016-11-30 14:57:49 -08:00
..
benchmark	Remove final references to PackageUriResolver	2016-09-07 13:03:19 -07:00
doc	Don't perform final fields and top-level variables type propagation.	2016-08-29 15:18:12 -07:00
example	Break up another large file	2016-09-15 07:49:27 -07:00
lib	Revert "Transition analyzer and analysis_server to new astFactory; remove old AST factory methods."	2016-11-30 14:57:49 -08:00
test	Revert "Transition analyzer and analysis_server to new astFactory; remove old AST factory methods."	2016-11-30 14:57:49 -08:00
tool	Split out options from ContextBuilder	2016-10-20 11:03:11 -07:00
.analysis_options	Make analyzer strong-mode clean	2016-08-01 11:55:15 -07:00
BUILD.gn	Add BUILD.gn for pkg/front_end to fix the Fuchsia build	2016-11-08 15:15:07 -08:00
CHANGELOG.md	Revert "Transition analyzer and analysis_server to new astFactory; remove old AST factory methods."	2016-11-30 14:57:49 -08:00
LICENSE
pubspec.yaml	Update analyzer pubspec to reflect dependency on collection.	2016-11-30 09:24:02 -08:00
README.md	Support the name analysis_options.yaml for analysis options files	2016-05-13 07:33:06 -07:00

README.md

Analyzer for Dart

This package provides a low-level library that performs static analysis of Dart code. It is useful for tool integration and embedding.

End-users should use the dartanalyzer command-line tool to analyze their Dart code.

Integrators that want to add Dart support to their editor should use the Dart Analysis Server. The Analysis Server API Specification is available. If you are adding Dart support to an editor or IDE, please let us know by emailing our list.

Configuring the analyzer

Both dartanalyzer and Dart Analysis Server can be configured with either an analysis_options.yaml or .analysis_options file. This YAML file can control which files and paths are analyzed, which lints are applied, and more.

If you are embedding the analyzer library in your project, you are responsible for finding the analysis options file, parsing it, and configuring the analyzer.

The analysis options file should live at the root of your project (for example, next to your pubspec.yaml). Different embedders of analyzer, such as dartanalyzer or Dart Analysis Server, may choose to find the file in various different ways. Consult their documentation to learn more.

Here is an example file that instructs the analyzer to ignore two files:

analyzer:
  exclude:
    - test/_data/p4/lib/lib1.dart
    - test/_data/p5/p5.dart
    - test/_data/bad*.dart
    - test/_brokendata/**

Note that you can use globs, as defined by the glob package.

Here is an example file that enables the analyzer's strong mode:

analyzer:
  strong-mode: true

Here is an example file that enables two lint rules:

linter:
  rules:
    - camel_case_types
    - empty_constructor_bodies

Check out all the available Dart lint rules.

You can combine the analyzer section and the linter section into a single configuration. Here is an example:

analyzer:
  exclude:
    - test/_data/p4/lib/lib1.dart
linter:
  rules:
    - camel_case_types

Who uses this library?

Many tools embed this library, such as:

dartfmt - a formatter for Dart code
dartdoc - a documentation generator for Dart code
Dart Analysis Server - a stateful server that supports IDEs and editors

Support

Post issues and feature requests at https://github.com/dart-lang/sdk/issues

Questions and discussions are welcome at the Dart Analyzer Discussion Group.

Background

The APIs in this package are, quite frankly, a mess at the moment. They were originally machine generated by a translator and were based on an earlier Java implementation. Several of the API's still look like their Java predecessors (or worse) rather than clean Dart API's.

In addition, there is currently no clean distinction between public and internal APIs. We plan to address this issue but doing so will, unfortunately, require a large number of breaking changes. We will try to minimize the pain this causes for our clients, but some pain is inevitable.

License

See the LICENSE file.