Paul Berry
7911b6a989
This CL fixes several minor bugs: - In info_builder.dart, we were trying to apply SourceInformation from the defining library to all its parts. - In NnbdMigrationTestBase, we were trying to fully migrate each file before processing any other files. We need to prepare each input, then process each input, then finalize each input. - In NodeBuilder, we were failing to send part file sources to NullabilityGraph.migrating(). As a result, methods declared in part files were being treated as already migrated, so they were getting the wrong kinds of nullability nodes. - In _ProvisionalApiTestBase, we were sometimes visiting parts before discovering what libraries they were part of, causing inconsistent resolution results. I'm hoping this will be sufficient to address https://github.com/dart-lang/sdk/issues/40670. Change-Id: I07d693b31b6cf64bc6f72126f5ef4792b29e5029 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/136521 Reviewed-by: Mike Fairhurst <mfairhurst@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and (less complete) Language Server Protocol support is documented
in tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.