mirror of
https://github.com/microsoft/language-server-protocol.git
synced 2025-12-23 08:48:16 +00:00
fix typo in glob pattern spec (#2132)
This commit is contained in:
parent
d1b1600963
commit
f20ba0702f
7 changed files with 11 additions and 11 deletions
|
|
@ -9836,7 +9836,7 @@
|
|||
"kind": "base",
|
||||
"name": "string"
|
||||
},
|
||||
"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`)"
|
||||
"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`)"
|
||||
},
|
||||
{
|
||||
"name": "matches",
|
||||
|
|
@ -14710,7 +14710,7 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
"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",
|
||||
"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",
|
||||
"since": "3.17.0"
|
||||
},
|
||||
{
|
||||
|
|
@ -14828,7 +14828,7 @@
|
|||
"kind": "base",
|
||||
"name": "string"
|
||||
},
|
||||
"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",
|
||||
"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",
|
||||
"since": "3.17.0"
|
||||
}
|
||||
]
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ export interface DocumentFilter {
|
|||
* A glob pattern, like `*.{ts,js}`.
|
||||
*
|
||||
* Glob patterns can have the following syntax:
|
||||
* - `*` to match one or more characters in a path segment
|
||||
* - `*` to match zero 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}`
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ export interface DidChangeWatchedFilesRegistrationOptions {
|
|||
/**
|
||||
* The glob pattern to watch relative to the base path. Glob patterns can have
|
||||
* the following syntax:
|
||||
* - `*` to match one or more characters in a path segment
|
||||
* - `*` to match zero 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 conditions (e.g. `**/*.{ts,js}` matches all TypeScript
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ export interface FileOperationPatternOptions {
|
|||
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 zero 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}`
|
||||
|
|
|
|||
|
|
@ -10306,7 +10306,7 @@
|
|||
"kind": "base",
|
||||
"name": "string"
|
||||
},
|
||||
"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`)"
|
||||
"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`)"
|
||||
},
|
||||
{
|
||||
"name": "matches",
|
||||
|
|
@ -16035,7 +16035,7 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
"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",
|
||||
"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",
|
||||
"since": "3.17.0"
|
||||
},
|
||||
{
|
||||
|
|
@ -16066,7 +16066,7 @@
|
|||
"kind": "base",
|
||||
"name": "string"
|
||||
},
|
||||
"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",
|
||||
"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",
|
||||
"since": "3.17.0"
|
||||
},
|
||||
{
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Pattern definitions used in file watchers and document filters.
|
|||
/**
|
||||
* The pattern to watch relative to the base path. Glob patterns can have
|
||||
* the following syntax:
|
||||
* - `*` to match one or more characters in a path segment
|
||||
* - `*` to match zero 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 conditions (e.g. `**/*.{ts,js}` matches all TypeScript
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ export interface FileOperationPatternOptions {
|
|||
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 zero 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}`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue