View Source GenLSP.Structures.DidChangeNotebookDocumentParams (gen_lsp v0.7.0)
The params sent in a change notebook document notification.
@since 3.17.0
Link to this section Summary
Functions
Fields
- notebook_document: The notebook document that did change. The version number points to the version after all provided changes have been applied. If only the text document content of a cell changes the notebook version doesn't necessarily have to change.
- change: The actual changes to the notebook document.The changes describe single state changes to the notebook document.
So if there are two changes c1 (at array index 0) and c2 (at array
index 1) for a notebook in state S then c1 moves the notebook 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 notebook using change events use the following approach:
- start with the same initial content
- apply the 'notebookDocument/didChange' notifications in the order you receive them.
- apply the
NotebookChangeEvent
s in a single notification in the order you receive them.
Link to this section Types
@type t() :: %GenLSP.Structures.DidChangeNotebookDocumentParams{ change: GenLSP.Structures.NotebookDocumentChangeEvent.t(), notebook_document: GenLSP.Structures.VersionedNotebookDocumentIdentifier.t() }
Link to this section Functions
fields
Fields
- notebook_document: The notebook document that did change. The version number points to the version after all provided changes have been applied. If only the text document content of a cell changes the notebook version doesn't necessarily have to change.
- change: The actual changes to the notebook document.The changes describe single state changes to the notebook document.
So if there are two changes c1 (at array index 0) and c2 (at array
index 1) for a notebook in state S then c1 moves the notebook 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 notebook using change events use the following approach:
- start with the same initial content
- apply the 'notebookDocument/didChange' notifications in the order you receive them.
- apply the
NotebookChangeEvent
s in a single notification in the order you receive them.