Brian Wilkerson
3641fc33d6
Sorry for the length of the CL. I couldn't really think of a good way to split it up further. The first pass was previously suggesting everything declared in scopes below the class level. This CL expands that to include everything declared in the current library. It does not include imported declarations. It also doesn't yet handle members suggested after a period. Those are both being handled by constributors. Please look over the tests carefully. There are more changes than I would have liked, although I think they're mostly for the better (as in, the suggestions are more accurate), but I could easily have missed an invalid change. Change-Id: I98b3cfc8440ee5da09a8e6828c946d65d8d77759 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/338482 Reviewed-by: Samuel Rawlins <srawlins@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Keerti Parthasarathy <keertip@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 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.