vscode-languageserver-protocol 3.17.0-next.9 → 3.17.2-next.1

package/lib/common/protocol.semanticTokens.d.ts

@@ -1,7 +1,7 @@
 import { TextDocumentIdentifier, Range, uinteger, SemanticTokensEdit, SemanticTokensLegend, SemanticTokens, SemanticTokensDelta } from 'vscode-languageserver-types';
 import { RequestHandler0, RequestHandler } from 'vscode-jsonrpc';
 import { ProtocolRequestType, ProtocolRequestType0, RegistrationType } from './messages';
-import { PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions, TextDocumentRegistrationOptions, StaticRegistrationOptions } from './protocol';
+import type { PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions, TextDocumentRegistrationOptions, StaticRegistrationOptions } from './protocol';
 /**
  * @since 3.16.0
  */
@@ -76,6 +76,28 @@ export interface SemanticTokensClientCapabilities {
      * Whether the client supports tokens that can span multiple lines.
      */
     multilineTokenSupport?: boolean;
+    /**
+     * Whether the client allows the server to actively cancel a
+     * semantic token request, e.g. supports returning
+     * LSPErrorCodes.ServerCancelled. If a server does the client
+     * needs to retrigger the request.
+     *
+     * @since 3.17.0
+     */
+    serverCancelSupport?: boolean;
+    /**
+     * Whether the client uses semantic tokens to augment existing
+     * syntax tokens. If set to `true` client side created syntax
+     * tokens and semantic tokens are both used for colorization. If
+     * set to `false` the client only uses the returned semantic tokens
+     * for colorization.
+     *
+     * If the value is `undefined` then the client behavior is not
+     * specified.
+     *
+     * @since 3.17.0
+     */
+    augmentsSyntaxTokens?: boolean;
 }
 /**
  * @since 3.16.0

package/lib/common/protocol.typeDefinition.d.ts

@@ -1,7 +1,7 @@
 import { RequestHandler } from 'vscode-jsonrpc';
 import { Definition, DefinitionLink, LocationLink, Location } from 'vscode-languageserver-types';
 import { ProtocolRequestType } from './messages';
-import { TextDocumentRegistrationOptions, StaticRegistrationOptions, TextDocumentPositionParams, PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions } from './protocol';
+import type { TextDocumentRegistrationOptions, StaticRegistrationOptions, TextDocumentPositionParams, PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions } from './protocol';
 /**
  * Since 3.6.0
  */

package/lib/common/{proposed.typeHierarchy.d.ts → protocol.typeHierarchy.d.ts}

@@ -1,44 +1,41 @@
 import { RequestHandler } from 'vscode-jsonrpc';
 import { TypeHierarchyItem } from 'vscode-languageserver-types';
 import { ProtocolRequestType } from './messages';
-import { TextDocumentRegistrationOptions, StaticRegistrationOptions, TextDocumentPositionParams, PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions } from './protocol';
+import type { TextDocumentRegistrationOptions, StaticRegistrationOptions, TextDocumentPositionParams, PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions } from './protocol';
 /**
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
-export interface TypeHierarchyClientCapabilities {
+export declare type TypeHierarchyClientCapabilities = {
     /**
      * Whether implementation supports dynamic registration. If this is set to `true`
      * the client supports the new `(TextDocumentRegistrationOptions & StaticRegistrationOptions)`
      * return value for the corresponding server capability as well.
      */
     dynamicRegistration?: boolean;
-}
+};
 /**
  * Type hierarchy options used during static registration.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
-export interface TypeHierarchyOptions extends WorkDoneProgressOptions {
-}
+export declare type TypeHierarchyOptions = WorkDoneProgressOptions;
 /**
  * Type hierarchy options used during static or dynamic registration.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
-export interface TypeHierarchyRegistrationOptions extends TextDocumentRegistrationOptions, TypeHierarchyOptions, StaticRegistrationOptions {
-}
+export declare type TypeHierarchyRegistrationOptions = TextDocumentRegistrationOptions & TypeHierarchyOptions & StaticRegistrationOptions;
 /**
  * The parameter of a `textDocument/prepareTypeHierarchy` request.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
-export interface TypeHierarchyPrepareParams extends TextDocumentPositionParams, WorkDoneProgressParams {
-}
+export declare type TypeHierarchyPrepareParams = TextDocumentPositionParams & WorkDoneProgressParams;
 /**
  * A request to result a `TypeHierarchyItem` in a document at a given position.
  * Can be used as an input to a subtypes or supertypes type hierarchy.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
 export declare namespace TypeHierarchyPrepareRequest {
     const method: 'textDocument/prepareTypeHierarchy';
@@ -48,15 +45,15 @@ export declare namespace TypeHierarchyPrepareRequest {
 /**
  * The parameter of a `typeHierarchy/supertypes` request.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
-export interface TypeHierarchySupertypesParams extends WorkDoneProgressParams, PartialResultParams {
+export declare type TypeHierarchySupertypesParams = WorkDoneProgressParams & PartialResultParams & {
     item: TypeHierarchyItem;
-}
+};
 /**
  * A request to resolve the supertypes for a given `TypeHierarchyItem`.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
 export declare namespace TypeHierarchySupertypesRequest {
     const method: 'typeHierarchy/supertypes';
@@ -66,15 +63,15 @@ export declare namespace TypeHierarchySupertypesRequest {
 /**
  * The parameter of a `typeHierarchy/subtypes` request.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
-export interface TypeHierarchySubtypesParams extends WorkDoneProgressParams, PartialResultParams {
+export declare type TypeHierarchySubtypesParams = WorkDoneProgressParams & PartialResultParams & {
     item: TypeHierarchyItem;
-}
+};
 /**
  * A request to resolve the subtypes for a given `TypeHierarchyItem`.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
 export declare namespace TypeHierarchySubtypesRequest {
     const method: 'typeHierarchy/subtypes';

package/lib/common/{proposed.typeHierarchy.js → protocol.typeHierarchy.js}

@@ -10,7 +10,7 @@ const messages_1 = require("./messages");
  * A request to result a `TypeHierarchyItem` in a document at a given position.
  * Can be used as an input to a subtypes or supertypes type hierarchy.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
 var TypeHierarchyPrepareRequest;
 (function (TypeHierarchyPrepareRequest) {
@@ -20,7 +20,7 @@ var TypeHierarchyPrepareRequest;
 /**
  * A request to resolve the supertypes for a given `TypeHierarchyItem`.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
 var TypeHierarchySupertypesRequest;
 (function (TypeHierarchySupertypesRequest) {
@@ -30,11 +30,11 @@ var TypeHierarchySupertypesRequest;
 /**
  * A request to resolve the subtypes for a given `TypeHierarchyItem`.
  *
- * @since 3.17.0 - proposed state
+ * @since 3.17.0
  */
 var TypeHierarchySubtypesRequest;
 (function (TypeHierarchySubtypesRequest) {
     TypeHierarchySubtypesRequest.method = 'typeHierarchy/subtypes';
     TypeHierarchySubtypesRequest.type = new messages_1.ProtocolRequestType(TypeHierarchySubtypesRequest.method);
 })(TypeHierarchySubtypesRequest = exports.TypeHierarchySubtypesRequest || (exports.TypeHierarchySubtypesRequest = {}));
-//# sourceMappingURL=proposed.typeHierarchy.js.map
+//# sourceMappingURL=protocol.typeHierarchy.js.map

package/lib/common/{protocol.workspaceFolders.d.ts → protocol.workspaceFolder.d.ts}

@@ -1,57 +1,27 @@
+import { WorkspaceFolder } from 'vscode-languageserver-types';
 import { RequestHandler0, NotificationHandler, HandlerResult, CancellationToken } from 'vscode-jsonrpc';
 import { ProtocolRequestType0, ProtocolNotificationType } from './messages';
 export interface WorkspaceFoldersInitializeParams {
     /**
      * The actual configured workspace folders.
      */
-    workspaceFolders: WorkspaceFolder[] | null;
-}
-export interface WorkspaceFoldersClientCapabilities {
-    /**
-     * The workspace client capabilities
-     */
-    workspace?: {
-        /**
-         * The client has support for workspace folders
-         *
-         * @since 3.6.0
-         */
-        workspaceFolders?: boolean;
-    };
+    workspaceFolders?: WorkspaceFolder[] | null;
 }
 export interface WorkspaceFoldersServerCapabilities {
     /**
-     * The workspace server capabilities
-     */
-    workspace?: {
-        workspaceFolders?: {
-            /**
-             * The Server has support for workspace folders
-             */
-            supported?: boolean;
-            /**
-             * Whether the server wants to receive workspace folder
-             * change notifications.
-             *
-             * If a strings is provided the string is treated as a ID
-             * under which the notification is registered on the client
-             * side. The ID can be used to unregister for these events
-             * using the `client/unregisterCapability` request.
-             */
-            changeNotifications?: string | boolean;
-        };
-    };
-}
-export interface WorkspaceFolder {
-    /**
-     * The associated URI for this workspace folder.
+     * The Server has support for workspace folders
      */
-    uri: string;
+    supported?: boolean;
     /**
-     * The name of the workspace folder. Used to refer to this
-     * workspace folder in the user interface.
+     * Whether the server wants to receive workspace folder
+     * change notifications.
+     *
+     * If a strings is provided the string is treated as a ID
+     * under which the notification is registered on the client
+     * side. The ID can be used to unregister for these events
+     * using the `client/unregisterCapability` request.
      */
-    name: string;
+    changeNotifications?: string | boolean;
 }
 /**
  * The `workspace/workspaceFolders` is sent from the server to the client to fetch the open workspace folders.

package/lib/common/{protocol.workspaceFolders.js → protocol.workspaceFolder.js}

@@ -21,4 +21,4 @@ var DidChangeWorkspaceFoldersNotification;
 (function (DidChangeWorkspaceFoldersNotification) {
     DidChangeWorkspaceFoldersNotification.type = new messages_1.ProtocolNotificationType('workspace/didChangeWorkspaceFolders');
 })(DidChangeWorkspaceFoldersNotification = exports.DidChangeWorkspaceFoldersNotification || (exports.DidChangeWorkspaceFoldersNotification = {}));
-//# sourceMappingURL=protocol.workspaceFolders.js.map
+//# sourceMappingURL=protocol.workspaceFolder.js.map

package/lib/node/main.js

@@ -5,7 +5,11 @@
  * ------------------------------------------------------------------------------------------ */
 var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
     if (k2 === undefined) k2 = k;
-    Object.defineProperty(o, k2, { enumerable: true, get: function() { return m[k]; } });
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
 }) : (function(o, m, k, k2) {
     if (k2 === undefined) k2 = k;
     o[k2] = m[k];