css-variable-lsp 1.0.0 → 1.0.2

package/client/node_modules/vscode-languageserver-protocol/lib/common/protocol.fileOperations.d.ts

@@ -1,306 +0,0 @@
-import { NotificationHandler, RequestHandler } from 'vscode-jsonrpc';
-import { WorkspaceEdit } from 'vscode-languageserver-types';
-import { MessageDirection, ProtocolNotificationType, ProtocolRequestType } from './messages';
-/**
- * Options for notifications/requests for user operations on files.
- *
- * @since 3.16.0
- */
-export interface FileOperationOptions {
-    /**
-    * The server is interested in receiving didCreateFiles notifications.
-    */
-    didCreate?: FileOperationRegistrationOptions;
-    /**
-    * The server is interested in receiving willCreateFiles requests.
-    */
-    willCreate?: FileOperationRegistrationOptions;
-    /**
-    * The server is interested in receiving didRenameFiles notifications.
-    */
-    didRename?: FileOperationRegistrationOptions;
-    /**
-    * The server is interested in receiving willRenameFiles requests.
-    */
-    willRename?: FileOperationRegistrationOptions;
-    /**
-    * The server is interested in receiving didDeleteFiles file notifications.
-    */
-    didDelete?: FileOperationRegistrationOptions;
-    /**
-    * The server is interested in receiving willDeleteFiles file requests.
-    */
-    willDelete?: FileOperationRegistrationOptions;
-}
-/**
- * The options to register for file operations.
- *
- * @since 3.16.0
- */
-export interface FileOperationRegistrationOptions {
-    /**
-     * The actual filters.
-     */
-    filters: FileOperationFilter[];
-}
-/**
- * A pattern kind describing if a glob pattern matches a file a folder or
- * both.
- *
- * @since 3.16.0
- */
-export declare namespace FileOperationPatternKind {
-    /**
-     * The pattern matches a file only.
-     */
-    const file: 'file';
-    /**
-     * The pattern matches a folder only.
-     */
-    const folder: 'folder';
-}
-export type FileOperationPatternKind = 'file' | 'folder';
-/**
- * Matching options for the file operation pattern.
- *
- * @since 3.16.0
- */
-export interface FileOperationPatternOptions {
-    /**
-     * The pattern should be matched ignoring casing.
-     */
-    ignoreCase?: boolean;
-}
-/**
- * A pattern to describe in which file operation requests or notifications
- * the server is interested in receiving.
- *
- * @since 3.16.0
- */
-interface FileOperationPattern {
-    /**
-     * The glob pattern to match. Glob patterns can have the following syntax:
-     * - `*` to match one or more characters in a path segment
-     * - `?` to match on one character in a path segment
-     * - `**` to match any number of path segments, including none
-     * - `{}` to group sub patterns into an OR expression. (e.g. `**​/*.{ts,js}` matches all TypeScript and JavaScript files)
-     * - `[]` to declare a range of characters to match in a path segment (e.g., `example.[0-9]` to match on `example.0`, `example.1`, …)
-     * - `[!...]` 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`)
-     */
-    glob: string;
-    /**
-     * Whether to match files or folders with this pattern.
-     *
-     * Matches both if undefined.
-     */
-    matches?: FileOperationPatternKind;
-    /**
-     * Additional options used during matching.
-     */
-    options?: FileOperationPatternOptions;
-}
-/**
- * A filter to describe in which file operation requests or notifications
- * the server is interested in receiving.
- *
- * @since 3.16.0
- */
-export interface FileOperationFilter {
-    /**
-     * A Uri scheme like `file` or `untitled`.
-     */
-    scheme?: string;
-    /**
-     * The actual file operation pattern.
-     */
-    pattern: FileOperationPattern;
-}
-/**
- * Capabilities relating to events from file operations by the user in the client.
- *
- * These events do not come from the file system, they come from user operations
- * like renaming a file in the UI.
- *
- * @since 3.16.0
- */
-export interface FileOperationClientCapabilities {
-    /**
-     * Whether the client supports dynamic registration for file requests/notifications.
-     */
-    dynamicRegistration?: boolean;
-    /**
-     * The client has support for sending didCreateFiles notifications.
-     */
-    didCreate?: boolean;
-    /**
-     * The client has support for sending willCreateFiles requests.
-     */
-    willCreate?: boolean;
-    /**
-     * The client has support for sending didRenameFiles notifications.
-     */
-    didRename?: boolean;
-    /**
-     * The client has support for sending willRenameFiles requests.
-     */
-    willRename?: boolean;
-    /**
-     * The client has support for sending didDeleteFiles notifications.
-     */
-    didDelete?: boolean;
-    /**
-     * The client has support for sending willDeleteFiles requests.
-     */
-    willDelete?: boolean;
-}
-/**
- * The parameters sent in notifications/requests for user-initiated creation of
- * files.
- *
- * @since 3.16.0
- */
-export interface CreateFilesParams {
-    /**
-     * An array of all files/folders created in this operation.
-     */
-    files: FileCreate[];
-}
-/**
- * Represents information on a file/folder create.
- *
- * @since 3.16.0
- */
-export interface FileCreate {
-    /**
-     * A file:// URI for the location of the file/folder being created.
-     */
-    uri: string;
-}
-/**
- * The parameters sent in notifications/requests for user-initiated renames of
- * files.
- *
- * @since 3.16.0
- */
-export interface RenameFilesParams {
-    /**
-     * An array of all files/folders renamed in this operation. When a folder is renamed, only
-     * the folder will be included, and not its children.
-     */
-    files: FileRename[];
-}
-/**
- * Represents information on a file/folder rename.
- *
- * @since 3.16.0
- */
-export interface FileRename {
-    /**
-     * A file:// URI for the original location of the file/folder being renamed.
-     */
-    oldUri: string;
-    /**
-     * A file:// URI for the new location of the file/folder being renamed.
-     */
-    newUri: string;
-}
-/**
- * The parameters sent in notifications/requests for user-initiated deletes of
- * files.
- *
- * @since 3.16.0
- */
-export interface DeleteFilesParams {
-    /**
-     * An array of all files/folders deleted in this operation.
-     */
-    files: FileDelete[];
-}
-/**
- * Represents information on a file/folder delete.
- *
- * @since 3.16.0
- */
-export interface FileDelete {
-    /**
-     * A file:// URI for the location of the file/folder being deleted.
-     */
-    uri: string;
-}
-/**
- * The will create files request is sent from the client to the server before files are actually
- * created as long as the creation is triggered from within the client.
- *
- * The request can return a `WorkspaceEdit` which will be applied to workspace before the
- * files are created. Hence the `WorkspaceEdit` can not manipulate the content of the file
- * to be created.
- *
- * @since 3.16.0
- */
-export declare namespace WillCreateFilesRequest {
-    const method: 'workspace/willCreateFiles';
-    const messageDirection: MessageDirection;
-    const type: ProtocolRequestType<CreateFilesParams, WorkspaceEdit | null, never, void, FileOperationRegistrationOptions>;
-    type HandlerSignature = RequestHandler<CreateFilesParams, WorkspaceEdit | undefined | null, void>;
-}
-/**
- * The did create files notification is sent from the client to the server when
- * files were created from within the client.
- *
- * @since 3.16.0
- */
-export declare namespace DidCreateFilesNotification {
-    const method: 'workspace/didCreateFiles';
-    const messageDirection: MessageDirection;
-    const type: ProtocolNotificationType<CreateFilesParams, FileOperationRegistrationOptions>;
-    type HandlerSignature = NotificationHandler<CreateFilesParams>;
-}
-/**
- * The will rename files request is sent from the client to the server before files are actually
- * renamed as long as the rename is triggered from within the client.
- *
- * @since 3.16.0
- */
-export declare namespace WillRenameFilesRequest {
-    const method: 'workspace/willRenameFiles';
-    const messageDirection: MessageDirection;
-    const type: ProtocolRequestType<RenameFilesParams, WorkspaceEdit | null, never, void, FileOperationRegistrationOptions>;
-    type HandlerSignature = RequestHandler<RenameFilesParams, WorkspaceEdit | undefined | null, void>;
-}
-/**
- * The did rename files notification is sent from the client to the server when
- * files were renamed from within the client.
- *
- * @since 3.16.0
- */
-export declare namespace DidRenameFilesNotification {
-    const method: 'workspace/didRenameFiles';
-    const messageDirection: MessageDirection;
-    const type: ProtocolNotificationType<RenameFilesParams, FileOperationRegistrationOptions>;
-    type HandlerSignature = NotificationHandler<RenameFilesParams>;
-}
-/**
- * The will delete files request is sent from the client to the server before files are actually
- * deleted as long as the deletion is triggered from within the client.
- *
- * @since 3.16.0
- */
-export declare namespace DidDeleteFilesNotification {
-    const method: 'workspace/didDeleteFiles';
-    const messageDirection: MessageDirection;
-    const type: ProtocolNotificationType<DeleteFilesParams, FileOperationRegistrationOptions>;
-    type HandlerSignature = NotificationHandler<DeleteFilesParams>;
-}
-/**
- * The did delete files notification is sent from the client to the server when
- * files were deleted from within the client.
- *
- * @since 3.16.0
- */
-export declare namespace WillDeleteFilesRequest {
-    const method: 'workspace/willDeleteFiles';
-    const messageDirection: MessageDirection;
-    const type: ProtocolRequestType<DeleteFilesParams, WorkspaceEdit | null, never, void, FileOperationRegistrationOptions>;
-    type HandlerSignature = RequestHandler<DeleteFilesParams, WorkspaceEdit | undefined | null, void>;
-}
-export {};

package/client/node_modules/vscode-languageserver-protocol/lib/common/protocol.fileOperations.js

@@ -1,101 +0,0 @@
-"use strict";
-/* --------------------------------------------------------------------------------------------
- * Copyright (c) Microsoft Corporation. All rights reserved.
- * Licensed under the MIT License. See License.txt in the project root for license information.
- * ------------------------------------------------------------------------------------------ */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.WillDeleteFilesRequest = exports.DidDeleteFilesNotification = exports.DidRenameFilesNotification = exports.WillRenameFilesRequest = exports.DidCreateFilesNotification = exports.WillCreateFilesRequest = exports.FileOperationPatternKind = void 0;
-const messages_1 = require("./messages");
-/**
- * A pattern kind describing if a glob pattern matches a file a folder or
- * both.
- *
- * @since 3.16.0
- */
-var FileOperationPatternKind;
-(function (FileOperationPatternKind) {
-    /**
-     * The pattern matches a file only.
-     */
-    FileOperationPatternKind.file = 'file';
-    /**
-     * The pattern matches a folder only.
-     */
-    FileOperationPatternKind.folder = 'folder';
-})(FileOperationPatternKind || (exports.FileOperationPatternKind = FileOperationPatternKind = {}));
-/**
- * The will create files request is sent from the client to the server before files are actually
- * created as long as the creation is triggered from within the client.
- *
- * The request can return a `WorkspaceEdit` which will be applied to workspace before the
- * files are created. Hence the `WorkspaceEdit` can not manipulate the content of the file
- * to be created.
- *
- * @since 3.16.0
- */
-var WillCreateFilesRequest;
-(function (WillCreateFilesRequest) {
-    WillCreateFilesRequest.method = 'workspace/willCreateFiles';
-    WillCreateFilesRequest.messageDirection = messages_1.MessageDirection.clientToServer;
-    WillCreateFilesRequest.type = new messages_1.ProtocolRequestType(WillCreateFilesRequest.method);
-})(WillCreateFilesRequest || (exports.WillCreateFilesRequest = WillCreateFilesRequest = {}));
-/**
- * The did create files notification is sent from the client to the server when
- * files were created from within the client.
- *
- * @since 3.16.0
- */
-var DidCreateFilesNotification;
-(function (DidCreateFilesNotification) {
-    DidCreateFilesNotification.method = 'workspace/didCreateFiles';
-    DidCreateFilesNotification.messageDirection = messages_1.MessageDirection.clientToServer;
-    DidCreateFilesNotification.type = new messages_1.ProtocolNotificationType(DidCreateFilesNotification.method);
-})(DidCreateFilesNotification || (exports.DidCreateFilesNotification = DidCreateFilesNotification = {}));
-/**
- * The will rename files request is sent from the client to the server before files are actually
- * renamed as long as the rename is triggered from within the client.
- *
- * @since 3.16.0
- */
-var WillRenameFilesRequest;
-(function (WillRenameFilesRequest) {
-    WillRenameFilesRequest.method = 'workspace/willRenameFiles';
-    WillRenameFilesRequest.messageDirection = messages_1.MessageDirection.clientToServer;
-    WillRenameFilesRequest.type = new messages_1.ProtocolRequestType(WillRenameFilesRequest.method);
-})(WillRenameFilesRequest || (exports.WillRenameFilesRequest = WillRenameFilesRequest = {}));
-/**
- * The did rename files notification is sent from the client to the server when
- * files were renamed from within the client.
- *
- * @since 3.16.0
- */
-var DidRenameFilesNotification;
-(function (DidRenameFilesNotification) {
-    DidRenameFilesNotification.method = 'workspace/didRenameFiles';
-    DidRenameFilesNotification.messageDirection = messages_1.MessageDirection.clientToServer;
-    DidRenameFilesNotification.type = new messages_1.ProtocolNotificationType(DidRenameFilesNotification.method);
-})(DidRenameFilesNotification || (exports.DidRenameFilesNotification = DidRenameFilesNotification = {}));
-/**
- * The will delete files request is sent from the client to the server before files are actually
- * deleted as long as the deletion is triggered from within the client.
- *
- * @since 3.16.0
- */
-var DidDeleteFilesNotification;
-(function (DidDeleteFilesNotification) {
-    DidDeleteFilesNotification.method = 'workspace/didDeleteFiles';
-    DidDeleteFilesNotification.messageDirection = messages_1.MessageDirection.clientToServer;
-    DidDeleteFilesNotification.type = new messages_1.ProtocolNotificationType(DidDeleteFilesNotification.method);
-})(DidDeleteFilesNotification || (exports.DidDeleteFilesNotification = DidDeleteFilesNotification = {}));
-/**
- * The did delete files notification is sent from the client to the server when
- * files were deleted from within the client.
- *
- * @since 3.16.0
- */
-var WillDeleteFilesRequest;
-(function (WillDeleteFilesRequest) {
-    WillDeleteFilesRequest.method = 'workspace/willDeleteFiles';
-    WillDeleteFilesRequest.messageDirection = messages_1.MessageDirection.clientToServer;
-    WillDeleteFilesRequest.type = new messages_1.ProtocolRequestType(WillDeleteFilesRequest.method);
-})(WillDeleteFilesRequest || (exports.WillDeleteFilesRequest = WillDeleteFilesRequest = {}));

package/client/node_modules/vscode-languageserver-protocol/lib/common/protocol.foldingRange.d.ts

@@ -1,109 +0,0 @@
-import { RequestHandler, RequestHandler0 } from 'vscode-jsonrpc';
-import { TextDocumentIdentifier, uinteger, FoldingRange, FoldingRangeKind } from 'vscode-languageserver-types';
-import { MessageDirection, ProtocolRequestType, ProtocolRequestType0 } from './messages';
-import type { TextDocumentRegistrationOptions, StaticRegistrationOptions, PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions } from './protocol';
-export interface FoldingRangeClientCapabilities {
-    /**
-     * Whether implementation supports dynamic registration for folding range
-     * providers. If this is set to `true` the client supports the new
-     * `FoldingRangeRegistrationOptions` return value for the corresponding
-     * server capability as well.
-     */
-    dynamicRegistration?: boolean;
-    /**
-     * The maximum number of folding ranges that the client prefers to receive
-     * per document. The value serves as a hint, servers are free to follow the
-     * limit.
-     */
-    rangeLimit?: uinteger;
-    /**
-     * If set, the client signals that it only supports folding complete lines.
-     * If set, client will ignore specified `startCharacter` and `endCharacter`
-     * properties in a FoldingRange.
-     */
-    lineFoldingOnly?: boolean;
-    /**
-     * Specific options for the folding range kind.
-     *
-     * @since 3.17.0
-     */
-    foldingRangeKind?: {
-        /**
-         * The folding range kind values the client supports. When this
-         * property exists the client also guarantees that it will
-         * handle values outside its set gracefully and falls back
-         * to a default value when unknown.
-         */
-        valueSet?: FoldingRangeKind[];
-    };
-    /**
-     * Specific options for the folding range.
-     *
-     * @since 3.17.0
-     */
-    foldingRange?: {
-        /**
-        * If set, the client signals that it supports setting collapsedText on
-        * folding ranges to display custom labels instead of the default text.
-        *
-        * @since 3.17.0
-        */
-        collapsedText?: boolean;
-    };
-}
-/**
- * Client workspace capabilities specific to folding ranges
- *
- * @since 3.18.0
- * @proposed
- */
-export interface FoldingRangeWorkspaceClientCapabilities {
-    /**
-     * Whether the client implementation supports a refresh request sent from the
-     * server to the client.
-     *
-     * Note that this event is global and will force the client to refresh all
-     * folding ranges currently shown. It should be used with absolute care and is
-     * useful for situation where a server for example detects a project wide
-     * change that requires such a calculation.
-     *
-     * @since 3.18.0
-     * @proposed
-     */
-    refreshSupport?: boolean;
-}
-export interface FoldingRangeOptions extends WorkDoneProgressOptions {
-}
-export interface FoldingRangeRegistrationOptions extends TextDocumentRegistrationOptions, FoldingRangeOptions, StaticRegistrationOptions {
-}
-/**
- * Parameters for a {@link FoldingRangeRequest}.
- */
-export interface FoldingRangeParams extends WorkDoneProgressParams, PartialResultParams {
-    /**
-     * The text document.
-     */
-    textDocument: TextDocumentIdentifier;
-}
-/**
- * A request to provide folding ranges in a document. The request's
- * parameter is of type {@link FoldingRangeParams}, the
- * response is of type {@link FoldingRangeList} or a Thenable
- * that resolves to such.
- */
-export declare namespace FoldingRangeRequest {
-    const method: 'textDocument/foldingRange';
-    const messageDirection: MessageDirection;
-    const type: ProtocolRequestType<FoldingRangeParams, FoldingRange[] | null, FoldingRange[], void, FoldingRangeRegistrationOptions>;
-    type HandlerSignature = RequestHandler<FoldingRangeParams, FoldingRange[] | null, void>;
-}
-/**
- * @since 3.18.0
- * @proposed
- */
-export declare namespace FoldingRangeRefreshRequest {
-    const method: `workspace/foldingRange/refresh`;
-    const messageDirection: MessageDirection;
-    const type: ProtocolRequestType0<void, void, void, void>;
-    type HandlerSignature = RequestHandler0<void, void>;
-}

package/client/node_modules/vscode-languageserver-protocol/lib/common/protocol.foldingRange.js

@@ -1,30 +0,0 @@
-"use strict";
-/*---------------------------------------------------------------------------------------------
- *  Copyright (c) Microsoft Corporation. All rights reserved.
- *  Licensed under the MIT License. See License.txt in the project root for license information.
- *--------------------------------------------------------------------------------------------*/
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.FoldingRangeRefreshRequest = exports.FoldingRangeRequest = void 0;
-const messages_1 = require("./messages");
-/**
- * A request to provide folding ranges in a document. The request's
- * parameter is of type {@link FoldingRangeParams}, the
- * response is of type {@link FoldingRangeList} or a Thenable
- * that resolves to such.
- */
-var FoldingRangeRequest;
-(function (FoldingRangeRequest) {
-    FoldingRangeRequest.method = 'textDocument/foldingRange';
-    FoldingRangeRequest.messageDirection = messages_1.MessageDirection.clientToServer;
-    FoldingRangeRequest.type = new messages_1.ProtocolRequestType(FoldingRangeRequest.method);
-})(FoldingRangeRequest || (exports.FoldingRangeRequest = FoldingRangeRequest = {}));
-/**
- * @since 3.18.0
- * @proposed
- */
-var FoldingRangeRefreshRequest;
-(function (FoldingRangeRefreshRequest) {
-    FoldingRangeRefreshRequest.method = `workspace/foldingRange/refresh`;
-    FoldingRangeRefreshRequest.messageDirection = messages_1.MessageDirection.serverToClient;
-    FoldingRangeRefreshRequest.type = new messages_1.ProtocolRequestType0(FoldingRangeRefreshRequest.method);
-})(FoldingRangeRefreshRequest || (exports.FoldingRangeRefreshRequest = FoldingRangeRefreshRequest = {}));

package/client/node_modules/vscode-languageserver-protocol/lib/common/protocol.implementation.d.ts

@@ -1,38 +0,0 @@
-import { RequestHandler } from 'vscode-jsonrpc';
-import { Definition, DefinitionLink, Location, LocationLink } from 'vscode-languageserver-types';
-import { MessageDirection, ProtocolRequestType } from './messages';
-import type { TextDocumentRegistrationOptions, StaticRegistrationOptions, TextDocumentPositionParams, PartialResultParams, WorkDoneProgressParams, WorkDoneProgressOptions } from './protocol';
-/**
- * @since 3.6.0
- */
-export interface ImplementationClientCapabilities {
-    /**
-     * Whether implementation supports dynamic registration. If this is set to `true`
-     * the client supports the new `ImplementationRegistrationOptions` return value
-     * for the corresponding server capability as well.
-     */
-    dynamicRegistration?: boolean;
-    /**
-     * The client supports additional metadata in the form of definition links.
-     *
-     * @since 3.14.0
-     */
-    linkSupport?: boolean;
-}
-export interface ImplementationOptions extends WorkDoneProgressOptions {
-}
-export interface ImplementationRegistrationOptions extends TextDocumentRegistrationOptions, ImplementationOptions, StaticRegistrationOptions {
-}
-export interface ImplementationParams extends TextDocumentPositionParams, WorkDoneProgressParams, PartialResultParams {
-}
-/**
- * A request to resolve the implementation locations of a symbol at a given text
- * document position. The request's parameter is of type {@link TextDocumentPositionParams}
- * the response is of type {@link Definition} or a Thenable that resolves to such.
- */
-export declare namespace ImplementationRequest {
-    const method: 'textDocument/implementation';
-    const messageDirection: MessageDirection;
-    const type: ProtocolRequestType<ImplementationParams, Definition | LocationLink[] | null, Location[] | LocationLink[], void, ImplementationRegistrationOptions>;
-    type HandlerSignature = RequestHandler<ImplementationParams, Definition | DefinitionLink[] | null, void>;
-}

package/client/node_modules/vscode-languageserver-protocol/lib/common/protocol.implementation.js

@@ -1,21 +0,0 @@
-"use strict";
-/* --------------------------------------------------------------------------------------------
- * Copyright (c) Microsoft Corporation. All rights reserved.
- * Licensed under the MIT License. See License.txt in the project root for license information.
- * ------------------------------------------------------------------------------------------ */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ImplementationRequest = void 0;
-const messages_1 = require("./messages");
-// @ts-ignore: to avoid inlining LocationLink as dynamic import
-let __noDynamicImport;
-/**
- * A request to resolve the implementation locations of a symbol at a given text
- * document position. The request's parameter is of type {@link TextDocumentPositionParams}
- * the response is of type {@link Definition} or a Thenable that resolves to such.
- */
-var ImplementationRequest;
-(function (ImplementationRequest) {
-    ImplementationRequest.method = 'textDocument/implementation';
-    ImplementationRequest.messageDirection = messages_1.MessageDirection.clientToServer;
-    ImplementationRequest.type = new messages_1.ProtocolRequestType(ImplementationRequest.method);
-})(ImplementationRequest || (exports.ImplementationRequest = ImplementationRequest = {}));