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

..

BuildServerBuildSystemTests.swift

Don’t rely on timers for BSP target / settings change tests

2024-10-24 18:00:41 -07:00

BuildSystemManagerTests.swift

Use fallback build settings if build system doesn’t provide build settings within a timeout

2024-10-16 10:55:29 -07:00

CompilationDatabasePerfTests.swift

Rename SKCore to BuildSystemIntegration

2024-07-25 09:11:13 -07:00

CompilationDatabaseTests.swift

Use withUnsafeFileSystemRepresentation to get the path of a URL on disk

2024-10-21 11:12:30 -07:00

FallbackBuildSettingsTests.swift

Use fallback build settings if build system doesn’t provide build settings within a timeout

2024-10-16 10:55:29 -07:00

LegacyBuildServerBuildSystemTests.swift

Use withUnsafeFileSystemRepresentation to get the path of a URL on disk

2024-10-21 11:12:30 -07:00

SplitShellCommandTests.swift

Rename SKCore to BuildSystemIntegration

2024-07-25 09:11:13 -07:00

SwiftPMBuildSystemTests.swift

Use build/taskStart, build/taskProgress and build/taskFinish to communicate progress from a BSP server to the client

2024-11-06 09:39:09 -08:00