Skip to content

Commit

Permalink
fix config schema error in CI
Browse files Browse the repository at this point in the history
  • Loading branch information
matthewbastien committed Jan 16, 2025
1 parent e55c244 commit ba46eb8
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 0 deletions.
3 changes: 3 additions & 0 deletions Documentation/Configuration File.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,9 @@ The structure of the file is currently not guaranteed to be stable. Options may
- `privacyLevel: "public"|"private"|"sensitive"`: Whether potentially sensitive information should be redacted. Default is `public`, which redacts potentially sensitive information.
- `inputMirrorDirectory: string`: Write all input received by SourceKit-LSP on stdin to a file in this directory. Useful to record and replay an entire SourceKit-LSP session.
- `outputMirrorDirectory: string`: Write all data sent from SourceKit-LSP to the client to a file in this directory. Useful to record the raw communication between SourceKit-LSP and the client on a low level.
- `sourcekitd`: Options modifying the behavior of sourcekitd.
- `clientPlugin: string`: When set, load the SourceKit client plugin from this path instead of locating it inside the toolchain.
- `servicePlugin: string`: When set, load the SourceKit service plugin from this path instead of locating it inside the toolchain.
- `defaultWorkspaceType: "buildServer"|"compilationDatabase"|"swiftPM"`: Default workspace type. Overrides workspace type selection logic.
- `generatedFilesPath: string`: Directory in which generated interfaces and macro expansions should be stored.
- `backgroundIndexing: boolean`: Whether background indexing is enabled.
Expand Down
17 changes: 17 additions & 0 deletions config.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,23 @@
},
"type" : "object"
},
"sourcekitd" : {
"description" : "Options modifying the behavior of sourcekitd.",
"markdownDescription" : "Options modifying the behavior of sourcekitd.",
"properties" : {
"clientPlugin" : {
"description" : "When set, load the SourceKit client plugin from this path instead of locating it inside the toolchain.",
"markdownDescription" : "When set, load the SourceKit client plugin from this path instead of locating it inside the toolchain.",
"type" : "string"
},
"servicePlugin" : {
"description" : "When set, load the SourceKit service plugin from this path instead of locating it inside the toolchain.",
"markdownDescription" : "When set, load the SourceKit service plugin from this path instead of locating it inside the toolchain.",
"type" : "string"
}
},
"type" : "object"
},
"sourcekitdRequestTimeout" : {
"description" : "The maximum duration that a sourcekitd request should be allowed to execute before being declared as timed out. In general, editors should cancel requests that they are no longer interested in, but in case editors don't cancel requests, this ensures that a long-running non-cancelled request is not blocking sourcekitd and thus most semantic functionality. In particular, VS Code does not cancel the semantic tokens request, which can cause a long-running AST build that blocks sourcekitd.",
"markdownDescription" : "The maximum duration that a sourcekitd request should be allowed to execute before being declared as timed out. In general, editors should cancel requests that they are no longer interested in, but in case editors don't cancel requests, this ensures that a long-running non-cancelled request is not blocking sourcekitd and thus most semantic functionality. In particular, VS Code does not cancel the semantic tokens request, which can cause a long-running AST build that blocks sourcekitd.",
Expand Down

0 comments on commit ba46eb8

Please sign in to comment.