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.
dartanalyzer and Dart Analysis Server can be configured
.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.
.analysis_options file should live
at the root of your project (for example, next to your
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
Many tools embed this library, such as:
Post issues and feature requests at https://github.com/dart-lang/sdk/issues
Questions and discussions are welcome at the Dart Analyzer Discussion Group.
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.
See the [LICENSE] file.
Lexical support for DEP 40 (Interface libraries). This does not include any semantic checking to ensure that the implementation libraries are compatible with the interface library.
Cleaned up the initialization of plugins. Clients are now required to initialize plugins, possibly using the utility method AnalysisEngine.processRequiredPlugins().
Removed the old task model and code that supported it. None of the removed code was intended to be public API, but might be in use anyway.
_embedder.yamldiscovery and processing.
configureContext()extracted from server).
AnalysisContext API for associating configuration data with contexts
OptionsProcessor extension point API changed to pass associated
AnalysisContext instance into the
ErrorHandlertypedef API fix.
.packagesfiles (issue 24126)
Add a PathFilter and AnalysisOptionsProvider utility classes to aid clients in excluding files from analysis when directed to do so by an options file.
UriResolver.resolveUri(..)now takes an optional
ResolutionCopier.visitAwaitExpressionto copy *Type fields.
ClassName?.staticMemberto match spec.
Fix some implementations of
UriResolver.resolveUri(..) that did not
properly handle the new
_sdkext(to play nicer with pub).
analyzer_clipackage. Files moved:
Add this to your package's pubspec.yaml file:
You can install packages from the command line:
$ pub get
Alternatively, your editor might support pub. Check the docs for your editor to learn more.
|0.27.3||Apr 13, 2016||Go to the documentation of analyzer 0.27.3||Download analyzer 0.27.3 archive|
|0.27.2||Feb 16, 2016||Go to the documentation of analyzer 0.27.2||Download analyzer 0.27.2 archive|
|0.27.1+2||Jan 5, 2016||Go to the documentation of analyzer 0.27.1+2||Download analyzer 0.27.1+2 archive|
|0.27.1+1||Dec 18, 2015||Go to the documentation of analyzer 0.27.1+1||Download analyzer 0.27.1+1 archive|
|0.27.1||Dec 16, 2015||Go to the documentation of analyzer 0.27.1||Download analyzer 0.27.1 archive|
|0.27.0||Dec 8, 2015||Go to the documentation of analyzer 0.27.0||Download analyzer 0.27.0 archive|
|0.26.4||Dec 7, 2015||Go to the documentation of analyzer 0.26.4||Download analyzer 0.26.4 archive|
|0.26.3||Nov 21, 2015||Go to the documentation of analyzer 0.26.3||Download analyzer 0.26.3 archive|
|0.26.2+1||Nov 4, 2015||Go to the documentation of analyzer 0.26.2+1||Download analyzer 0.26.2+1 archive|
|0.26.2||Nov 2, 2015||Go to the documentation of analyzer 0.26.2||Download analyzer 0.26.2 archive|