Outside requirements #406
adam-fowler
started this conversation in
General
Replies: 1 comment 2 replies
-
Perhaps give swiftlang/sourcekit-lsp#601 a shot as it’s one of the main blockers for #386. It’s hard to pass all the configurations to SK-LSP, but much easier if we can use destination file directly. Also wants to mention how CLion deals with corelib/stdlib jump-to-definitions: it preloads all the available modules, generates |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Outside requirements
This is a list of issues added to other projects that would improve the VS Code Swift extension. I will try to keep this up to date as new requirements/bugs appear or are resolved.
Features
CodeAction
text will be formatted by another process. SourceKit-LSP should be doing this formatting. [SR-16106] Once SourceKit-LSP supports formatting, run formatter on text inserted by CodeActions sourcekit-lsp#496textDocument/diagnostic
support. [SR-16080] SourceKit-LSP isn't aware of changes in other files sourcekit-lsp#500swift package describe
Add snippet folder to swift package describe output swift-package-manager#5750Bugs
workspace-state.json
isn't updated when dependency removed. If it was we could use it as a source of truth for project dependencies Removing a dependency from the Package.swift does not remove it from workspace-state.json swift-package-manager#5727Beta Was this translation helpful? Give feedback.
All reactions