Kishikawa Katsumi SourceKit-LSPΛ࢖ͬͯWeb ϒϥ΢βͰSwiftͷೖྗิ׬Λ࣮ݱ͢Δ

໨࣍ 1. SwiftFiddle (Online Playground) Demo 2. ඪ४ϥΠϒϥϦͷؔ਺ͳͲΛίʔυิ׬͢Δ 1. SourceKit-LSPͱ௨৴͢Δ 2. Text Document Synchronization 3. γεςϜߏ੒ͱ࣮૷

SwiftFiddle Demo https://www.swiftfiddle.com/

No content

No content

No content

ඪ४ϥΠϒϥϦͷؔ਺ͳͲΛ ίʔυิ׬͢Δ

No content

SourceKit-LSPͱ௨৴͢Δ Client SourceKit-LSP initialize initialized didOpen hover hover definitions hover references

SourceKit-LSPͱ௨৴͢Δ Client SourceKit-LSP initialize didOpen hover { workspace: ~/projects/MySwiftApp } { documentURI: src/main.swift, text: "import Foundation ..." } { documentURI: src/main.swift, position: { row: 32, col: 7} }

SourceKit-LSPͱ௨৴͢Δ Client SourceKit-LSP initialize didOpen hover { workspace: ~/projects/MySwiftApp } { documentURI: src/main.swift, text: "import Foundation ..." } { documentURI: src/main.swift, position: { row: 32, col: 7} }

SourceKit-LSPͱ௨৴͢Δ Client SourceKit-LSP didOpen didChange { documentURI: src/main.swift, version: 2, contentChanges: ... } didChange { ..., version: 3, contentChanges: ... } completion

Text Document Synchronization Client support for textDocument/didOpen, textDocument/ didChange and textDocument/didClose notifications is mandatory in the protocol and clients can not opt out supporting them. This includes both full and incremental syncronization in the textDocument/didChange notification. In addition a server must either implement all three of them or none. Their capabilities are therefore controlled via a combined client and server capability. https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_synchronization

https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_synchronization

Text Document Synchronization The actual content changes. The content changes describe single state changes to the document. So if there are two content changes c1 (at array index 0) and c2 (at array index 1) for a document in state S then c1 moves the document from S to S' and c2 from S' to S''. So c1 is computed on the state S and c2 is computed on the state S'. To mirror the content of a document using change events use the following approach: - start with the same initial content - apply the 'textDocument/didChange' notifications in the order you recevie them. - apply the `TextDocumentContentChangeEvent`s in a single notification in the order you receive them. https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_synchronization

Text Document Synchronization S contentChange contentChange contentChange didChange

Text Document Synchronization S contentChange contentChange contentChange didChange S′

Text Document Synchronization S′ contentChange contentChange didChange S′′

Text Document Synchronization /// A change to a text document. /// /// If `range` and `rangeLength` are unspecified, /// the whole document content is replaced. /// public struct TextDocumentContentChangeEvent: Codable, Hashable { https://github.com/apple/sourcekit-lsp

Text Document Synchronization https://github.com/kishikawakatsumi/swift-playground

No content

LSP

No content

No content

No content

No content

No content

No content

No content

No content

GitHub Codespaces

GitHub Codespaces

References • https://swiftfiddle.com • https://github.com/kishikawakatsumi/swift-playground • https://github.com/kishikawakatsumi/SwiftFiddleEditor • https://github.com/kishikawakatsumi/SourceKitForSafari • https://github.com/apple/sourcekit-lsp • https://microsoft.github.io/language-server-protocol/ • https://ace.c9.io/