You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Edits the edits to be applied. 3.16.0 - support for AnnotatedTextEdit. This is guarded using a client capability. 3.18.0 - support for SnippetTextEdit. This is guarded using a client capability.
// ChangeAnnotation additional information that describes document changes.
@@ -401,7 +401,7 @@ type WorkspaceEdit struct {
401
401
402
402
// DocumentChanges depending on the client capability `workspace.workspaceEdit.resourceOperations` document changes are
403
403
// either an array of `TextDocumentEdit`s to express changes to n different text documents where each text document edit addresses a specific version of a text document. Or it can contain above `TextDocumentEdit`s mixed with create, rename and delete file / folder operations. Whether a client supports versioned document edits is expressed via `workspace.workspaceEdit.documentChanges` client capability. If a client neither supports `documentChanges` nor `workspace.workspaceEdit.resourceOperations` then only plain `TextEdit`s using the `changes` property are supported.
// ChangeAnnotations a map of change annotations that can be referenced in `AnnotatedTextEdit`s or create, rename and delete file / folder operations. Whether clients honor this property depends on the client capability `workspace.changeAnnotationSupport`.
@@ -1272,7 +1272,7 @@ type InlayHintLabelPart struct {
1272
1272
// Tooltip the tooltip text when you hover over this label part. Depending on the client capability `inlayHint.resolveSupport` clients might resolve this property late using the resolve request.
// Location an optional source code location that represents this label part. The editor will use this location for the hover and for code navigation features: This part will become a clickable link that resolves
1278
1278
// to the definition of the symbol at the given location (not necessarily the location itself), it shows the hover that shows at the given location, and it shows a context menu with further code navigation commands. Depending on the client capability `inlayHint.resolveSupport` clients might resolve this property late using the resolve request.
@@ -1299,7 +1299,7 @@ type InlayHint struct {
1299
1299
// Label the label of this hint. A human readable string or an array of InlayHintLabelPart label parts. *Note* that neither the string nor the label part can be empty.
// PaddingLeft render padding before the hint. Note: Padding should use the editor's background color, not the background color of the hint itself. That means padding can be used to visually align/separate an inlay hint.
1321
1321
//
@@ -1411,7 +1411,7 @@ type FullDocumentDiagnosticReport struct {
// TextEdit an TextEdit edit which is applied to a document when selecting this completion. When an edit is provided the value of CompletionItem.insertText insertText is ignored. Most editors support two different operations when accepting a completion item. One is to insert a completion text and the other is to replace an existing text with a completion text. Since this can usually not be predetermined by a server it can report both ranges. Clients need to signal support for `InsertReplaceEdits` via the `textDocument.completion.insertReplaceSupport` client capability property. *Note 1:* The text edit's range as well as both ranges from an insert replace edit must be a [single line] and they must contain the position at which completion has been requested. *Note 2:* If an `InsertReplaceEdit` is returned the edit's insert range must be a prefix of the edit's replace range, that means it must be contained and starting at the same position. 3.16.0 additional type `InsertReplaceEdit`.
// TextEditText the edit text used if the completion item is part of a CompletionList and CompletionList defines an item default for the text edit range. Clients will only honor this property if they opt into completion list item defaults using the capability `completionList.itemDefaults`. If not provided and a list's default range is provided the label property is used as a text.
1915
1915
TextEditTextstring`json:"textEditText,omitempty"`
@@ -1950,7 +1950,7 @@ type CompletionItemDefaults struct {
// Range an optional range inside the text document that is used to visualize the hover, e.g. by changing the
2018
2018
// background color.
@@ -2030,10 +2030,13 @@ type HoverRegistrationOptions struct {
2030
2030
typeParameterInformationstruct {
2031
2031
// Label the label of this parameter information. Either a string or an inclusive start and exclusive end offsets within its containing signature label. (see SignatureInformation.label). The offsets are based on a UTF-16 string representation as `Position` and `Range` does. To avoid ambiguities a server should use the [start, end] offset value instead of using a substring. Whether a client support this is controlled via `labelOffsetSupport` client capability. *Note*: a label of type string should be a substring of its containing signature label. Its intended use case is to highlight the parameter label
2032
2032
// part in the `SignatureInformation.label`.
2033
-
LabelParameterInformationLabel`json:"label"`
2033
+
LabelOneOf[string, struct {
2034
+
xuint32
2035
+
yuint32
2036
+
}] `json:"label"`
2034
2037
2035
2038
// Documentation the human-readable doc-comment of this parameter. Will be shown in the UI but can be omitted.
// SignatureInformation represents the signature of something callable. A signature can have a label, like a function-name, a doc-comment, and a set of parameters.
@@ -2042,7 +2045,7 @@ type SignatureInformation struct {
2042
2045
Labelstring`json:"label"`
2043
2046
2044
2047
// Documentation the human-readable doc-comment of this signature. Will be shown in the UI but can be omitted.
@@ -2608,7 +2611,7 @@ type RelatedFullDocumentDiagnosticReport struct {
2608
2611
2609
2612
// RelatedDocuments diagnostics of related documents. This information is useful in programming languages where code in a file A can generate diagnostics in a file B which A depends on. An example of such a language is C/C++ where marco definitions in a file a.cpp and result in errors in a header file b.hpp.
// RelatedUnchangedDocumentDiagnosticReport an unchanged diagnostic report with a set of related documents.
@@ -2620,7 +2623,7 @@ type RelatedUnchangedDocumentDiagnosticReport struct {
2620
2623
2621
2624
// RelatedDocuments diagnostics of related documents. This information is useful in programming languages where code in a file A can generate diagnostics in a file B which A depends on. An example of such a language is C/C++ where marco definitions in a file a.cpp and result in errors in a header file b.hpp.
@@ -2728,7 +2731,7 @@ type NotebookCellTextDocumentFilter struct {
2728
2731
// Notebook a filter that matches against the notebook containing the notebook cell. If a string value is provided it matches against the notebook type. '*' matches every notebook.
0 commit comments