Alex Hoppen
b01ae2adb6
Add Task{Start|Progress|Finish}Notification to BuildSystemMessageDependencyTracker
2024-11-15 17:02:53 -08:00
Alex Hoppen
8c2def8ef9
Rename SKSupport to LanguageServerProtocolExtensions
2024-11-13 16:53:58 -08:00
Alex Hoppen
06f58db5c8
Use build/taskStart, build/taskProgress and build/taskFinish to communicate progress from a BSP server to the client
...
Instead of defining BSP extensions for `window/workDoneProgress/create` and `$/progress`, we should be able to use the standard `build/taskStart`, `build/taskProgress` and `build/taskFinish` messages to the same effect, as suggested by https://forums.swift.org/t/extending-functionality-of-build-server-protocol-with-sourcekit-lsp/74400/9 .
Fixes #1783
rdar://138653131
2024-11-06 09:39:09 -08:00
Alex Hoppen
7befd0c648
Share implementation of message handling on an AsyncQueue between BuildSystemIntegration and SourceKitLSPServer
...
This gives us cancellation support for `BuiltInBuildSystemAdapter`.
2024-09-30 10:42:46 -07:00
Alex Hoppen
a9578bbb45
Review BuildSystemMessageDependencyTracker
2024-09-16 10:12:08 -07:00
Alex Hoppen
85b2f1fd30
Review BuildServerProtocol module for consistency
2024-09-16 10:10:26 -07:00
Alex Hoppen
5870ad9eb4
Implement InverseSourcesRequest in BuildSystemManager
...
`buildTarget/inverseSources` is not required to be implemented by BSP servers and we have almost all information needed for it in `BuildSystemManager`.
This also makes sure that `buildTarget/sources` and `buildTarget/inverseSources` actually match each other. Before this change, we had source files like `Package.swift` for which we returned a target from `buildTarget/inverseSources` but that weren’t part of that target’s sources retrieved using `buildTarget/sources`.
2024-09-16 10:08:14 -07:00
Alex Hoppen
f741b0dd41
Use more fine-grained dependency tracking to allow BSP requests to be handled concurrently
2024-09-16 10:06:35 -07:00
