Kenzie Davisson
0787d1eeec
This CL: - changes the name of the `ConnectedApp.getVmServiceUris` service method to `ConnectedApp.getVmServices` since the response includes more than just the URI for each VM service object. - Adds a new response type `VmServicesResponse` - Enhances test coverage for existing response types Work towards https://github.com/dart-lang/sdk/issues/60540. Change-Id: Id4a1c05dde28c9b23975ad1d2ca68cb9e2bddb22 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/430545 Reviewed-by: Ben Konyi <bkonyi@google.com> Commit-Queue: Kenzie Davisson <kenzieschmoll@google.com>
Dart Tooling Daemon
The server implementation for the Dart Tooling Daemon. This is meant to be run by our internal tooling and facilitates communication between our internal tools.
For details on the protocol used to communicate with the Dart Tooling Daemon see The DTD Protocol
Running the Dart Tooling Daemon
Compiled version
To run the tooling daemon compiled with the Dart SDK:
- make sure to build with
create_platform_sdk - e.g.
./tools/build.py create_platform_sdk
- run
dart tooling-daemon:info The dart binary should be the one you just built in step 1.
Testing changes locally
To quickly test changes to the tooling daemon, start it by running:
dart run bin/dtd.dart
Running tests
To run the tests under the test/ directory, run dart test test/.
However, if you are testing changes that span pkg/dtd and pkg/dtd_impl,
you'll need to build the Dart SDK, and then use the built Dart executable to run
the test.
- Build the Dart SDK:
./tools/build.py create_platform_sdk - Run the test:
xcodebuild/ReleaseARM64/dart-sdk/bin/dart test test/