languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-19 20:51:50 +00:00
Code Issues Packages Projects Releases Wiki Activity
dart-sdk/pkg/analysis_server
History
Danny Tuppeny 341b60796a [analysis_server] Generate typedefs for LSP params/result unions 
Many params/result types are defined as unions without names in the spec. This gives them names so the handlers will be able to use names instead of the full EitherX<Y> type.

Change-Id: I3f96b48e5e70c86814724edc3fec4fc7f76534de
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/248801
Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
2022-06-16 16:11:21 +00:00
..
benchmark Fix typos 2022-06-15 11:08:28 +00:00
bin [analysis_server] re-enble null safety for the analysis server entrypoint 2021-05-13 17:18:15 +00:00
doc [analysis_server] Set Container() as final tabstop/selection in Flutter snippets 2022-05-25 18:57:28 +00:00
lib [analysis_server] Generate typedefs for LSP params/result unions 2022-06-16 16:11:21 +00:00
test [analysis_server] Generate typedefs for LSP params/result unions 2022-06-16 16:11:21 +00:00
tool [analysis_server] Generate typedefs for LSP params/result unions 2022-06-16 16:11:21 +00:00
analysis_options.yaml [analysis_server] Removing ignoring hash_and_equals lint 2022-06-09 19:36:43 +00:00
AUTHORS
CHANGELOG.md
CONTRIBUTING.md
LICENSE Update LICENSE 2021-04-07 10:28:38 +00:00
OWNERS [infra] Add OWNERS to the Dart SDK 2022-02-14 14:06:34 +00:00
pubspec.yaml [pkg/analysis_server] remove some references to package:html 2022-06-13 20:00:28 +00:00
README.md "master->main" migration 2021-09-09 18:14:36 +00:00

README.md

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.