This plan captures our work in April. We will ship in early May. This is a 4-week iteration.
The endgame details for this iteration are tracked in https://github.com/microsoft/vscode/issues/96277.
Below is a summary of the top level plan items.
Legend of annotations:
| Mark | Description |
| ------------------- | ------------------------------------------------- |
| :runner: | work in progress |
| :hand: | blocked task |
| :muscle: | stretch goal for this iteration |
| :red_circle: | missing issue reference |
| :large_blue_circle: | more investigation required to remove uncertainty |
| :black_circle: | under discussion within the team |
Open With... https://github.com/microsoft/vscode/issues/94408 @rebornix teamxterm.js: Prepare client/server separation for terminals https://github.com/xtermjs/xterm.js/issues/2749 @tyriarI don't understand why you are putting this item to the Iteration Plan Item list
Support for custom views with WebView contents #83911 mjbvz
If it's not planned for this iteration.
Is it difficult to solve half a year's worth of proposals?
Word navigation in QuickOpen
https://github.com/microsoft/vscode/issues/84755
I would like to ask which iteration can specifically improve the efficiency of java coding. Many functions of Red Hat's Java language service cannot keep up with the development steps of Eclipse.
Why doesn't Microsoft develop or maintain the Java language service engine extension by itself? I look forward to Microsoft's own development of a Java language service engine extension based on Eclipse JDT, which will be more friendly, convenient, and rapid for the overall VSCode Java update iteration.
Because of the Java development extensions provided by Microsoft so far, only the core Java language service engine extension is missing. This is very regrettable.
much needed
Could you implement a separate extension host for type commands this iteration or the next?
The Vim keyboard lag is awful at times.
https://github.com/microsoft/vscode/issues/75627
Vim users feel like second class citizens in VSCode right now.
are you guys planning to fix export from jupyter to python script during this iteration?
Below the OPEN EDITORS section header does not have a background color and the VSCODE and OUTLINE headers have an upper border.
This isn't good way of UI. It's visually messing up sections. It's when designers taking over UI and putting style above productivity. The good way of UI is when each section on screen that is not related to each other should have visual contrast separation. That's why nobody liked Office 2013.
And this also not only about visual separation. It's also about eye attention for collapsed sections. When it's different your eye can quickly find it.
Most helpful comment
Could you implement a separate extension host for type commands this iteration or the next?
The Vim keyboard lag is awful at times.
https://github.com/microsoft/vscode/issues/75627
Vim users feel like second class citizens in VSCode right now.