Skip to content

Commit 172bbfa

Browse files
committed
Merge remote-tracking branch 'origin/gh-pages' into issue-98
2 parents 894b121 + 696f3f7 commit 172bbfa

File tree

7 files changed

+19
-40
lines changed

7 files changed

+19
-40
lines changed

Gemfile.lock

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -289,7 +289,7 @@ GEM
289289
tzinfo (2.0.6)
290290
concurrent-ruby (~> 1.0)
291291
unicode-display_width (1.8.0)
292-
uri (1.0.3)
292+
uri (1.0.4)
293293
webrick (1.9.1)
294294

295295
PLATFORMS

_implementors/servers.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -197,6 +197,7 @@ index: 1
197197
| [PromQL](https://prometheus.io/docs/prometheus/latest/querying/basics/) | [Tobias Guggenmos](https://github.com/slrtbtfs) | [promql-langserver](https://github.com/prometheus-community/promql-langserver) | [Go](https://golang.org/) |
198198
| [Protocol Buffers](https://protobuf.dev/) | [coder3101](https://github.com/coder3101) | [protols](https://github.com/coder3101/protols) | Rust |
199199
| [Protocol Buffers](https://protobuf.dev/) | [lasorda](https://github.com/lasorda) | [protobuf-language-server](https://github.com/lasorda/protobuf-language-server) | Go |
200+
| [Protocol Buffers](https://protobuf.dev/) | [Buf](https://github.com/bufbuild) | [Buf Language Server](https://github.com/bufbuild/buf) | Go |
200201
| PureScript | [Nicholas Wolverson](https://github.com/nwolverson) | [purescript-language-server](https://github.com/nwolverson/purescript-language-server) | PureScript |
201202
| Puppet| [Lingua Pupuli](https://github.com/lingua-pupuli) | [puppet language server](https://github.com/lingua-pupuli/puppet-editor-services) | Ruby |
202203
| Python | [astral-sh](https://astral.sh/) | [ty](https://github.com/astral-sh/ty) | Rust |
@@ -320,4 +321,5 @@ index: 1
320321
| * | [Sonar](https://github.com/SonarSource) | [SonarLint Language Server](https://github.com/SonarSource/sonarlint-language-server) | Java |
321322
| * | [kbwo](https://github.com/kbwo) | [testing-language-server](https://github.com/kbwo/testing-language-server) | Rust |
322323
| * | [GitHub](https://github.com/github/copilot-language-server-release) | [@github/copilot-language-server](https://www.npmjs.com/package/@github/copilot-language-server) (no code repository available, issues and feature requests can be done) | JavaScript |
324+
| * | [Automattic](https://github.com/Automattic) | [harper](https://github.com/Automattic/harper) | Rust |
323325
{: .table .table-bordered .table-responsive}

_specifications/lsp/3.17/language/signatureHelp.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -221,9 +221,9 @@ export interface SignatureHelp {
221221
* lies outside the range of `signatures[activeSignature].parameters`
222222
* defaults to 0 if the active signature has parameters. If
223223
* the active signature has no parameters it is ignored.
224-
* In future version of the protocol this property might become
225-
* mandatory to better express the active parameter if the
226-
* active signature does have any.
224+
*
225+
* Since version 3.16.0 the `SignatureInformation` itself provides a
226+
* `activeParameter` property and it should be used instead of this one.
227227
*/
228228
activeParameter?: uinteger;
229229
}

_specifications/lsp/3.17/notebookDocument/notebook.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -234,7 +234,7 @@ The protocol will therefore support two modes when it comes to synchronizing cel
234234
* _cellContent_: in this mode only the cell text content is synchronized to the server using the standard `textDocument/did*` notification. No notebook document and no cell structure is synchronized. This mode allows for easy adoption of notebooks since servers can reuse most of it implementation logic.
235235
* _notebook_: in this mode the notebook document, the notebook cells and the notebook cell text content is synchronized to the server. To allow servers to create a consistent picture of a notebook document the cell text content is NOT synchronized using the standard `textDocument/did*` notifications. It is instead synchronized using special `notebookDocument/did*` notifications. This ensures that the cell and its text content arrives on the server using one open, change or close event.
236236

237-
In both modes, notebook cell text documents are treated as regular text documents. Therefore, they use the same synchronization mechanism as specified by the server's `textDocumentSync` capability. For the _notebook_ mode, the cell text content changes sent via `notebookDocument/didChange` follow the same full/incremental change format as `textDocument/didChange`, respecting the `TextDocumentSyncKind` specified in `textDocumentSync.change`.
237+
In both modes, notebook cell text documents are treated as regular text documents. They are always synchronized using incremental sync.
238238

239239
To request the cell content only a normal document selector can be used. For example the selector `[{ language: 'python' }]` will synchronize Python notebook document cells to the server. However since this might synchronize unwanted documents as well a document filter can also be a `NotebookCellTextDocumentFilter`. So `{ notebook: { scheme: 'file', notebookType: 'jupyter-notebook' }, language: 'python' }` synchronizes all Python cells in a Jupyter notebook stored on disk.
240240

@@ -507,12 +507,6 @@ export interface NotebookDocumentChangeEvent {
507507

508508
/**
509509
* Changes to the text content of notebook cells.
510-
*
511-
* Cell text content changes follow the same synchronization mode
512-
* as specified by the server's `textDocumentSync.change` capability.
513-
* If `textDocumentSync.change` is `TextDocumentSyncKind.Incremental`,
514-
* clients should send incremental updates. If it is
515-
* `TextDocumentSyncKind.Full`, clients must send the full content.
516510
*/
517511
textContent?: {
518512
document: VersionedTextDocumentIdentifier;

_specifications/lsp/3.18/language/signatureHelp.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -240,9 +240,8 @@ export interface SignatureHelp {
240240
*
241241
* If the active signature has no parameters, it is ignored.
242242
*
243-
* In future versions of the protocol this property might become
244-
* mandatory (but still nullable) to better express the active parameter if
245-
* the active signature does have any.
243+
* Since version 3.16.0 the `SignatureInformation` itself provides a
244+
* `activeParameter` property and it should be used instead of this one.
246245
*/
247246
activeParameter?: uinteger | null;
248247
}

_specifications/lsp/3.18/metaModel/metaModel.json

Lines changed: 9 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -6401,22 +6401,6 @@
64016401
{
64026402
"name": "RenameParams",
64036403
"properties": [
6404-
{
6405-
"name": "textDocument",
6406-
"type": {
6407-
"kind": "reference",
6408-
"name": "TextDocumentIdentifier"
6409-
},
6410-
"documentation": "The document to rename."
6411-
},
6412-
{
6413-
"name": "position",
6414-
"type": {
6415-
"kind": "reference",
6416-
"name": "Position"
6417-
},
6418-
"documentation": "The position at which this request was sent."
6419-
},
64206404
{
64216405
"name": "newName",
64226406
"type": {
@@ -6426,6 +6410,12 @@
64266410
"documentation": "The new name of the symbol. If the given name is not valid the\nrequest must return a {@link ResponseError} with an\nappropriate message set."
64276411
}
64286412
],
6413+
"extends": [
6414+
{
6415+
"kind": "reference",
6416+
"name": "TextDocumentPositionParams"
6417+
}
6418+
],
64296419
"mixins": [
64306420
{
64316421
"kind": "reference",
@@ -10308,7 +10298,7 @@
1030810298
"kind": "base",
1030910299
"name": "string"
1031010300
},
10311-
"documentation": "The glob pattern to match. Glob patterns can have the following syntax:\n- `*` to match zero or more characters in a path segment\n- `?` to match on one character in a path segment\n- `**` to match any number of path segments, including none\n- `{}` to group sub patterns into an OR expression. (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)\n- `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)\n- `[!...]` to negate a range of characters to match in a path segment (e.g., `example.[!0-9]` to match on `example.a`, `example.b`, but not `example.0`)"
10301+
"documentation": "The glob pattern to match. Glob patterns can have the following syntax:\n- `*` to match one or more characters in a path segment\n- `?` to match on one character in a path segment\n- `**` to match any number of path segments, including none\n- `{}` to group sub patterns into an OR expression. (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)\n- `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)\n- `[!...]` to negate a range of characters to match in a path segment (e.g., `example.[!0-9]` to match on `example.a`, `example.b`, but not `example.0`)"
1031210302
},
1031310303
{
1031410304
"name": "matches",
@@ -16164,7 +16154,7 @@
1616416154
}
1616516155
]
1616616156
},
16167-
"documentation": "A document filter denotes a document by different properties like\nthe {@link TextDocument.languageId language}, the {@link Uri.scheme scheme} of\nits resource, or a glob-pattern that is applied to the {@link TextDocument.fileName path}.\n\nGlob patterns can have the following syntax:\n- `*` to match zero or more characters in a path segment\n- `?` to match on one character in a path segment\n- `**` to match any number of path segments, including none\n- `{}` to group sub patterns into an OR expression. (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)\n- `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)\n- `[!...]` to negate a range of characters to match in a path segment (e.g., `example.[!0-9]` to match on `example.a`, `example.b`, but not `example.0`)\n\n@sample A language filter that applies to typescript files on disk: `{ language: 'typescript', scheme: 'file' }`\n@sample A language filter that applies to all package.json paths: `{ language: 'json', pattern: '**package.json' }`\n\n@since 3.17.0",
16157+
"documentation": "A document filter denotes a document by different properties like\nthe {@link TextDocument.languageId language}, the {@link Uri.scheme scheme} of\nits resource, or a glob-pattern that is applied to the {@link TextDocument.fileName path}.\n\nGlob patterns can have the following syntax:\n- `*` to match one or more characters in a path segment\n- `?` to match on one character in a path segment\n- `**` to match any number of path segments, including none\n- `{}` to group sub patterns into an OR expression. (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)\n- `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)\n- `[!...]` to negate a range of characters to match in a path segment (e.g., `example.[!0-9]` to match on `example.a`, `example.b`, but not `example.0`)\n\n@sample A language filter that applies to typescript files on disk: `{ language: 'typescript', scheme: 'file' }`\n@sample A language filter that applies to all package.json paths: `{ language: 'json', pattern: '**package.json' }`\n\n@since 3.17.0",
1616816158
"since": "3.17.0"
1616916159
},
1617016160
{
@@ -16195,7 +16185,7 @@
1619516185
"kind": "base",
1619616186
"name": "string"
1619716187
},
16198-
"documentation": "The glob pattern to watch relative to the base path. Glob patterns can have the following syntax:\n- `*` to match zero or more characters in a path segment\n- `?` to match on one character in a path segment\n- `**` to match any number of path segments, including none\n- `{}` to group conditions (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)\n- `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)\n- `[!...]` to negate a range of characters to match in a path segment (e.g., `example.[!0-9]` to match on `example.a`, `example.b`, but not `example.0`)\n\n@since 3.17.0",
16188+
"documentation": "The glob pattern to watch relative to the base path. Glob patterns can have the following syntax:\n- `*` to match one or more characters in a path segment\n- `?` to match on one character in a path segment\n- `**` to match any number of path segments, including none\n- `{}` to group conditions (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)\n- `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)\n- `[!...]` to negate a range of characters to match in a path segment (e.g., `example.[!0-9]` to match on `example.a`, `example.b`, but not `example.0`)\n\n@since 3.17.0",
1619916189
"since": "3.17.0"
1620016190
},
1620116191
{

_specifications/lsp/3.18/notebookDocument/notebook.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ The protocol will therefore support two modes when it comes to synchronizing cel
252252
* _cellContent_: in this mode, only the cell text content is synchronized to the server using the standard `textDocument/did*` notification. No notebook document and no cell structure is synchronized. This mode allows for easy adoption of notebooks since servers can reuse most of their implementation logic.
253253
* _notebook_: in this mode the notebook document, the notebook cells and the notebook cell text content is synchronized to the server. To allow servers to create a consistent picture of a notebook document, the cell text content is NOT synchronized using the standard `textDocument/did*` notifications. It is instead synchronized using special `notebookDocument/did*` notifications. This ensures that the cell and its text content arrive on the server using one open, change or close event.
254254

255-
In both modes, notebook cell text documents are treated as regular text documents. Therefore, they use the same synchronization mechanism as specified by the server's `textDocumentSync` capability. For the _notebook_ mode, the cell text content changes sent via `notebookDocument/didChange` follow the same full/incremental change format as `textDocument/didChange`, respecting the `TextDocumentSyncKind` specified in `textDocumentSync.change`.
255+
In both modes, notebook cell text documents are treated as regular text documents. They are always synchronized using incremental sync.
256256

257257
To request the cell content, only a normal document selector can be used. For example, the selector `[{ language: 'python' }]` will synchronize Python notebook document cells to the server. However, since this might synchronize unwanted documents as well, a document filter can also be a `NotebookCellTextDocumentFilter`. So `{ notebook: { scheme: 'file', notebookType: 'jupyter-notebook' }, language: 'python' }` synchronizes all Python cells in a Jupyter notebook stored on disk.
258258

@@ -525,12 +525,6 @@ export interface NotebookDocumentChangeEvent {
525525

526526
/**
527527
* Changes to the text content of notebook cells.
528-
*
529-
* Cell text content changes follow the same synchronization mode
530-
* as specified by the server's `textDocumentSync.change` capability.
531-
* If `textDocumentSync.change` is `TextDocumentSyncKind.Incremental`,
532-
* clients should send incremental updates. If it is
533-
* `TextDocumentSyncKind.Full`, clients must send the full content.
534528
*/
535529
textContent?: {
536530
document: VersionedTextDocumentIdentifier;

0 commit comments

Comments
 (0)