When Apple’s VS Code extension has been released prompt to install it #40
Comments
First step into this direction: as sourcekit-lsp is now included in Xcode by default, we switched the default LSP to it in 2.10.0 |
Does SourceKit work better in VSCode than it does in Xcode? I feel like it's pretty terrible in Xcode and I lose syntax highlighting all the time. |
@tylerjames all, Xcode, sourcekite and sourcekit-lsp rely on SourceKit and therefore share lots of the same problems. Especially for non-SwiftPM projects, using VS Code requires a greater initial effort and doesn't provide a few features Xcode can provide (running and debugging on iOS/on Simulators, refactorings, Swift Migrations, code coverage views, ...). But the syntax highlighting in VS Code is more stable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once the extension has been released to VS Code‘s extension registry and it is stable enough, we need to add a warning to prefer that instead if not installed yet.
This should be an opt-out.
More details:
https://www.vknabel.com/pages/Apples-SourceKit-LSP-and-SDE-Roadmap/
The text was updated successfully, but these errors were encountered: