Owen Voorhees
f04b971726
Adopt swift-tools-protocols
2025-10-31 14:11:11 -07:00
Alex Hoppen
95538e7de9
Migrate appendingPathComponent to appending(component:)
...
`appending(component:)` is the more modern API and can take multiple path components at the same time.
2025-09-23 16:57:56 +02:00
Alex Hoppen
509ac6f9be
Replace a couple of #if conditions by runtime checks
...
This ensures that we build all branches on all platforms, reducing the likelihood of build failures on other platforms.
2025-08-25 23:33:17 +02:00
Owen Voorhees
dd5800c712
Port SwiftPMBuildSystemTests to Swift Testing
2025-06-15 16:35:29 -07:00
Alex Hoppen
1cfa8db1d8
Require Swift 6 to build SourceKit-LSP
...
This significantly cleans up our `import` statements
2025-03-07 08:05:49 -08:00
Alex Hoppen
b33a42f0ab
When using SOURCEKIT_LSP_TEST_PLUGIN_PATHS=RELATIVE_TO_SOURCEKITD infer plugin paths from default testing toolchain
...
Otherwise, we infer the SourceKit plugin paths from the toolchain when creating a `SourceKitLSPServer` during testing because we don’t override the plugin paths in the SourceKitLSPOptions. But when running `SourceKitDTests`, we pass `pluginPaths: nil`, which would not load any plugins. If both of the tests run in the same process, this causes a fault to get logged because sourcekitd can only loaded once per process and we can’t modify which plugins are loaded after the fact.
2025-02-05 08:23:04 -08:00
Alex Hoppen
8787787e4f
Allow loading the SourceKit plugin from the toolchain during testing
2025-01-27 09:18:45 -08:00
Alex Hoppen
425102ea93
When the SourceKit plugins fail to load during testing, include the search base in the error
2025-01-24 13:03:41 -08:00
Alex Hoppen
16f897aefa
Make the SourceKit plugins work on Windows
2025-01-11 06:57:03 +01:00
Alex Hoppen
e5f1bbfc03
Set plugin paths in all tests
...
Otherwise, we were trying to load sourcekitd without the plugins for the normal SourceKIt-LSP tests and with the plugins for the plugin tests.
2025-01-09 14:09:01 +01:00
