-
Notifications
You must be signed in to change notification settings - Fork 307
Add a request to re-index all files in SourceKit-LSP #1507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci Please test |
Documentation/LSP Extensions.md
Outdated
|
||
New request to re-index all files open in the SourceKit-LSP server. | ||
|
||
Users should not need to rely on this request. The index should always be updated automatically in the background. Having to invoke this request manes there is a bug in SourceKit-LSP's automatic re-indexing. It does, however, offer a workaround to re-index files when such a bug occurs where otherwise there would be no workaround. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users should not need to rely on this request. The index should always be updated automatically in the background. Having to invoke this request manes there is a bug in SourceKit-LSP's automatic re-indexing. It does, however, offer a workaround to re-index files when such a bug occurs where otherwise there would be no workaround. | |
Users should not need to rely on this request. The index should always be updated automatically in the background. Having to invoke this request means there is a bug in SourceKit-LSP's automatic re-indexing. It does, however, offer a workaround to re-index files when such a bug occurs where otherwise there would be no workaround. |
Sources/LanguageServerProtocol/Requests/TriggerReindexRequest.swift
Outdated
Show resolved
Hide resolved
@swift-ci Please test |
@swift-ci Please test Windows |
@@ -697,6 +697,8 @@ extension SourceKitLSPServer: MessageHandler { | |||
await request.reply { try await pollIndex(request.params) } | |||
case let request as RequestAndReply<BarrierRequest>: | |||
await request.reply { VoidResponse() } | |||
case let request as RequestAndReply<TriggerReIndexRequest>: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I'd go with TriggerReindexRequest
as ReIndex
looks really odd to me. But 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was debating whether to capitalize the I
and wasn’t sure whether in a sentence re-index or reindex would be the preferred spelling. Changed it to lowercase i
.
Users should not need to rely on this request. The index should always be updated automatically in the background. Having to invoke this request manes there is a bug in SourceKit-LSP's automatic re-indexing. It does, however, offer a workaround to re-index files when such a bug occurs where otherwise there would be no workaround. rdar://127476221 Resolves swiftlang#1263
@swift-ci Please test |
Users should not need to rely on this request. The index should always be updated automatically in the background. Having to invoke this request manes there is a bug in SourceKit-LSP's automatic re-indexing. It does, however, offer a workaround to re-index files when such a bug occurs where otherwise there would be no workaround.
rdar://127476221
Resolves #1263