This plan captures what we work on during February. We will ship early March.
Not unusual and still noteworthy: We will do several explorations that might or might not result in concrete deliverables in this or later releases.
The endgame for this iteration is tracked in #20981.
Below is a summary of the top level plan items.
Legend for annotations:
| Mark | Description |
| ------------- | ------------- |
| :runner: | work in progress |
| :hand: | blocked task |
| :muscle: | stretch goal for this iteration |
| :large_blue_circle: | more details required |
| :red_circle: | missing issue reference |
task.json, v2 shows the task output in the terminal @dbaeumertsconfig.json validation (see also Microsoft/TypeScript#12336) #20163node2 and node into a single node debugging experience #19650 @weinand @roblourens :hand: Support large extension, adopt new marketplace support #18146 @joaomoreno
Keyboard layout improvements #17521 @alexandrudima
If "Explore: Move the preferences for theme, icon theme from local storage to settings @aeschli @sandy081" means per-workspace theme settings, then YES PLEASE!
I expect this feature to appear in the iteration plan, thanks.
Or, VSCode provides an API to Extension author to set the encoding of the file.
Hoping that the «HTML: Analyze Live preview options» , will solve, eventually, the problems with some of the HTML preview extensions available :D.
Basically: «not working» or «only working when the HTML tab is focused and the changes are done directly in the tab» (rendering it useless if you use any kind of template engine that generates HTML).
@soulchainer what HTML preview extensions have you tried? Can you send me an email wade.[email protected]?
Closing 1.10 has shipped.
Most helpful comment
I expect this feature to appear in the iteration plan, thanks.
Automatically detect encoding of the file opened #5388
Or, VSCode provides an API to Extension author to set the encoding of the file.