gen_lsp v0.8.1

View Source GenLSP.Structures.DidChangeTextDocumentParams (gen_lsp v0.8.1)

The change text document notification's parameters.

Link to this section Summary

Types

t()

Functions

%GenLSP.Structures.DidChangeTextDocumentParams{}

Fields

  • text_document: The document that did change. The version number points to the version after all provided content changes have been applied.
  • content_changes: 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 receive them.
    • apply the TextDocumentContentChangeEvents in a single notification in the order you receive them.

Link to this section Types

Link to this type

t()

View Source 
@type t() :: %GenLSP.Structures.DidChangeTextDocumentParams{
  content_changes: [GenLSP.TypeAlias.TextDocumentContentChangeEvent.t()],
  text_document: GenLSP.Structures.VersionedTextDocumentIdentifier.t()
}

Link to this section Functions

Link to this function

%GenLSP.Structures.DidChangeTextDocumentParams{}

View Source (struct)

fields

 Fields

  • text_document: The document that did change. The version number points to the version after all provided content changes have been applied.
  • content_changes: 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 receive them.
    • apply the TextDocumentContentChangeEvents in a single notification in the order you receive them.