Change:
resolveCompletionItem?(item: T, token: CancellationToken): ProviderResult<T>; } <ins> /** * The inline completion item provider interface defines the contract between extensions and * the inline completion feature. * * Providers are asked for completions either explicitly by a user gesture or implicitly when typing. */ export interface InlineCompletionItemProvider { /** * Provides inline completion items for the given position and document. * If inline completions are enabled, this method will be called whenever the user stopped typing. * It will also be called when the user explicitly triggers inline completions or explicitly asks for the next or previous inline completion. * In that case, all available inline completions should be returned. * `context.triggerKind` can be used to distinguish between these scenarios. * * @param document The document inline completions are requested for. * @param position The position inline completions are requested for. * @param context A context object with additional information. * @param token A cancellation token. * @return An array of completion items or a thenable that resolves to an array of completion items. */ provideInlineCompletionItems(document: TextDocument, position: Position, context: InlineCompletionContext, token: CancellationToken): ProviderResult<InlineCompletionItem[] | InlineCompletionList>; } /** * Represents a collection of {@link InlineCompletionItem inline completion items} to be presented * in the editor. */ export class InlineCompletionList { /** * The inline completion items. */ items: InlineCompletionItem[]; /** * Creates a new list of inline completion items. */ constructor(items: InlineCompletionItem[]); } /** * Provides information about the context in which an inline completion was requested. */ export interface InlineCompletionContext { /** * Describes how the inline completion was triggered. */ readonly triggerKind: InlineCompletionTriggerKind; /** * Provides information about the currently selected item in the autocomplete widget if it is visible. * * If set, provided inline completions must extend the text of the selected item * and use the same range, otherwise they are not shown as preview. * As an example, if the document text is `console.` and the selected item is `.log` replacing the `.` in the document, * the inline completion must also replace `.` and start with `.log`, for example `.log()`. * * Inline completion providers are requested again whenever the selected item changes. */ readonly selectedCompletionInfo: SelectedCompletionInfo | undefined; } /** * Describes the currently selected completion item. */ export interface SelectedCompletionInfo { /** * The range that will be replaced if this completion item is accepted. */ readonly range: Range; /** * The text the range will be replaced with if this completion is accepted. */ readonly text: string; } /** * Describes how an {@link InlineCompletionItemProvider inline completion provider} was triggered. */ export enum InlineCompletionTriggerKind { /** * Completion was triggered explicitly by a user gesture. * Return multiple completion items to enable cycling through them. */ Invoke = 0, /** * Completion was triggered automatically while editing. * It is sufficient to return a single completion item in this case. */ Automatic = 1, } /** * An inline completion item represents a text snippet that is proposed inline to complete text that is being typed. * * @see {@link InlineCompletionItemProvider.provideInlineCompletionItems} */ export class InlineCompletionItem { /** * The text to replace the range with. Must be set. * Is used both for the preview and the accept operation. */ insertText: string | SnippetString; /** * A text that is used to decide if this inline completion should be shown. When `falsy` * the {@link InlineCompletionItem.insertText} is used. * * An inline completion is shown if the text to replace is a prefix of the filter text. */ filterText?: string; /** * The range to replace. * Must begin and end on the same line. * * Prefer replacements over insertions to provide a better experience when the user deletes typed text. */ range?: Range; /** * An optional {@link Command} that is executed *after* inserting this completion. */ command?: Command; /** * Creates a new inline completion item. * * @param insertText The text to replace the range with. * @param range The range to replace. If not set, the word at the requested position will be used. * @param command An optional {@link Command} that is executed *after* inserting this completion. */ constructor(insertText: string | SnippetString, range?: Range, command?: Command); } </ins> /** * A document link is a range in a text document that links to an internal or external resource, like another * text document or a web site.

Discussion:
(edited by We use this issue to track the progress of the Inline Completions API. The currently proposed API can be found in . There is a sample extension . Before this API can be finalized, we need to figure out these items at least: [x] How can inline completions interact with completions? (Currently, inline completions are hidden when autocomplete shows up and if there is an inline completion, autocomplete does not show up automatically)
why is this proposal not still open? Normally for proposals, we keep them open until the api is finalized and shipped. So that users/extension authors can track the proposal more easily.
Trying to copy and get 404. Is this link dead? This makes the sample in vscode: useless as well. Can you please help?
They have an updated way to get the file. First you have to change the to in the file. Then run to download the latest version of and then run . See more (if the link doesn't scroll down to the "updated api proposal structure" you have to control f it).
Hi folks! Is the API still likely to be released in April as mentioned in ?
it is currently assigned to April and that is our plan. It might slip to May depending on how testing and feedback from Extensions that use this proposed API goes. I suggest to follow this issue for more details. Thanks!
Hello! While trying out the sample package (). I receive the following errors. I also attempted the method you specified and the methods mentioned in the readme. In addition, I also tried the following npm commands: Npm install Npm run postinstall Is this sample still up to date?
good catch. I have tackled the outdated extension via this PR Once we get it approved I will merge it in and then the sample should be up to date. Thanks
Looks like this is on mainline? Any idea when it will be released beyond insiders?
this is assigned to the May milestone. Which means it is part of our May release which usually gets shipped first 10 days of the following month. So this one should be available on Thursday.
amazing! Thanks so much for getting back to me, I'll be deving accordingly :)
I have opened this discussion for any follow up questions since we have done the finalization