Danny Tuppeny
eed5d692ab
It's possible that there are nested paths in LSP workspace folders, such as: /foo /fooBar /bar/foo We shouldn't just replace each path we were given, as it might replace the wrong parts of other parts. Instead, require the path to be surrounded by quotes, or prefixed by a quote and followed by the appropriate path separator. I also tweaked the benchmark test a little to report the time for the first call separately from the others, since that one triggers the regex build. On my machine, timings currently are: ``` Replacing 250 paths in payload of 2097152 bytes Iteration #1, First: 43ms, Rest: 30ms Iteration #2, First: 38ms, Rest: 30ms Iteration #3, First: 33ms, Rest: 30ms Iteration #4, First: 37ms, Rest: 30ms Iteration #5, First: 31ms, Rest: 29ms ``` Change-Id: I75de1fb36a16636e0f50099cced1d5386318d589 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/491640 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Samuel Rawlins <srawlins@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.