Adopt SnippetString API
See original GitHub issueWith the December release VS Code will have real API to define a CompletionItem that is inserted as snippet, for details see https://github.com/Microsoft/vscode/issues/3210.
In short, we now support a subset of the more common TextMate syntax: $1
, $2
etc define tabstops, ${1:value}
and ${2:this is${3:nested}}
placeholders, and $0
is for the final tabstop.
The API for this is contained in a new type SnippetString
. It can be used as the insertText
of a CompletionItem.
During a transition phase we will still support the internal, unspecified snippet syntax your extension is using but eventually remove it (roughly 2 or 3 milestones from now).
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Adopt SnippetString API #99 - redhat-developer/vscode-java
The API for this is contained in a new type SnippetString . It can be used as the insertText of a CompletionItem. During...
Read more >Extension Guides - Visual Studio Code
Learn from Visual Studio Code extension guides and code samples.
Read more >Manage creatives for buyers | Buyer APIs - Google Developers
You can do the following as a buyer: Create and submit creatives for review; View existing creatives; Patch existing creatives. Submit creatives ...
Read more >vscode.SnippetString - Haxe externs for Visual Studio Code
A snippet string is a template which allows to insert text and to control the editor cursor when insertion happens.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great, thanks for the heads up!
Note-to-me: Here’s an example of this migration (TypeScript) as a reference.
I think the issue is that the internal API used underscore as the final cursor position (see https://github.com/Microsoft/vscode/issues/6874#issuecomment-235606255) but in 1.8 it renders a real underscore.