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
Copy file name to clipboardExpand all lines: src/@types/vscode.proposed.chatContextProvider.d.ts
+3-10Lines changed: 3 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -16,10 +16,7 @@ declare module 'vscode' {
16
16
* Providers registered without a selector will not be called for resource-based context.
17
17
* - Explicitly. These context items are shown as options when the user explicitly attaches context.
18
18
*
19
-
* To ensure your extension is activated when chat context is requested, make sure to include the following activations events:
20
-
* - If your extension implements `provideWorkspaceChatContext` or `provideChatContextForResource`, find an activation event which is a good signal to activate.
* - If your extension implements `provideChatContextExplicit`, your extension will be automatically activated when the user requests explicit context.
19
+
* To ensure your extension is activated when chat context is requested, make sure to include the `onChatContextProvider:<id>` activation event in your `package.json`.
23
20
*
24
21
* @param selector Optional document selector to filter which resources the provider is called for. If omitted, the provider will only be called for explicit context requests.
25
22
* @param id Unique identifier for the provider.
@@ -52,7 +49,7 @@ declare module 'vscode' {
52
49
value?: string;
53
50
/**
54
51
* An optional command that is executed when the context item is clicked.
55
-
* The original context item will be passed as the first argument to the command.
52
+
* The original context item will be passed as an argument to the command.
56
53
*/
57
54
command?: Command;
58
55
}
@@ -65,11 +62,7 @@ declare module 'vscode' {
65
62
onDidChangeWorkspaceChatContext?: Event<void>;
66
63
67
64
/**
68
-
* TODO @API: should this be a separate provider interface?
69
-
*
70
-
* Provide a list of chat context items to be included as workspace context for all chat requests.
71
-
* This should be used very sparingly to avoid providing useless context and to avoid using up the context window.
72
-
* A good example use case is to provide information about which branch the user is working on in a source control context.
65
+
* Provide a list of chat context items to be included as workspace context for all chat sessions.
0 commit comments