Paul Berry
48aa6470ca
Now there are only two circumstances in which an AtomicEdit won't have information about the reason for the change: - The AtomicEdit object was associated with adding or removing parens, in which case we don't compute information about the reason for the change because it's not straightforward to compute, and it should be clear to the user anyway. - Information about the reason for the change hasn't been plumbed through properly (this should be addressed in follow-up CLs). Since we are rapidly approaching a situation where nearly all AtomicEdits will have reason information, the separation between AtomicEdit and AtomicEditWithInfo now seems silly, so I just moved the `info` object into AtomicEdit and removed AtomicEditWithInfo entirely. Change-Id: I61afd9cd58b71d4695685e65d0142a2693b8e6b2 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/132451 Reviewed-by: Brian Wilkerson <brianwilkerson@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.