Iteration Plan for March 2024

[kieferrm]

This plan captures our work in March. This is a 5-week iteration. We will ship in early April.

Endgame

• March 25, 2024: Endgame begins
• March 28, 2024: Endgame done

The endgame details for this iteration are tracked here.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Accessibility

• Add context actions to Comments view vscode#5741 @alexr00
• Inform users of running cells and inline suggestions in notebooks vscode#176288 @amunger
• Accessibility issues, see query @meganrogge team

Workbench

• Improve quick pick experiences, see query @TylerLeonhardt
• Adopt the multi-file diff editor for rendering refactor previews vscode#204370 @aiday-mar @hediet @jrieken
• Support moving webviews to aux window vscode#195715 @bpasero @rebornix @mjbvz
• Move activity bar to bottom vscode#118692 @benibenj
• Allow custom editor labels vscode#41909 @benibenj @bpasero
• Synchronized Scrolling in Split Editor vscode#33110 @benibenj
• Allow to easily stage code from the diff editor vscode#206808 @hediet

Code Editor

• Explore using the new EditContext API vscode#204371 @hediet
• 🏃 Explore hover enriching vscode#195394 @aiday-mar @hediet
• Merge rendering logic of PR "Support dynamic line heights using decorations #194609" @hediet
• Explore tree-sitter parser ecosystem @alexr00 vscode#207416
• Missing quick fixes immediately after introducing an error vscode#117812 @justschen
• 🏃 Multi-file diff editor has no TabInput vscode#206411 @lramos15 @hediet
• Release the Monaco Editor CHANGELOG @hediet

Search

• Polish the quick search preview editor experience vscode#204853 @andreamah

Authentication

• Prevent logging in with multiple GitHub accounts while its not supported vscode#203850 @TylerLeonhardt

Notebook Editor

• 🏃 Polish variables view vscode#203480 @amunger
• Explore run in section in sticky scroll / outline / Go to Symbols vscode#199992 @Yoyokrazy
• Polish outline view entries for notebook vscode#206308 @Yoyokrazy
• 🏃 Explore notebook level formatting support vscode#207334 @Yoyokrazy @rebornix
• Notebook edit history polish (timeline, undo/redo of notebook operations) vscode#205634 @DonJayamanne
• Support browser keybindings (arrow, pageup/down, shift+pageup/down, ctrl+a) vscode#206747 @DonJayamanne
• Remove custom entry from Jupyter notebook metadata (coordinate with .NET and Julia) vscode#205637 @DonJayamanne

Jupyter Notebooks

• Update Codespace with latest Kernel Provider api vscode-jupyter#15125 @DonJayamanne
• Support module import/usage analysis in Run Dependent Cells vscode-jupyter#14674 @rebornix w/ Pylance team

WebAssembly Support

• 🏃 Document how to use VS Code's component model tooling to use WASM services inside a VS Code extensions vscode-wasm#157 @dbaeumer

Issue Reporter

• 🏃 Explore supporting the issue reporter in the web @justschen

Languages

Python

• Contributions to the Python extension, see plan @karthiknadig team

TypeScript

• ✋ Automatic type acquisition on the web vscode#172887 @mjbvz
• 🏃 Support bringing along imports with copy paste typescript#50187 @mjbvz
• Adopt CodeAction ranges for refactorings @mjbvz
• Ship TypeScript 5.4 @mjbvz
• 🏃 Use vscode watches for tsserver vscode#193848 @bpasero
• Explore adoption of new issue reporter command contribution in TS extension @justschen

Terminal

• Release xterm.js 5.4 [email protected] @Tyriar
• Explore automatic glyph scaling opt-out vscode#206342 @Tyriar
• 🏃 Explore exposing shell integration command knowledge to extensions vscode#145234 @Tyriar

Source Control

• Quick diff decorators for incoming changes vscode#204982 @lszomoru

Testing

• 🏃 Finalize test coverage API vscode#123713 @connor4312

Debug

• 🏃 Expose current thread/stack frame id vscode#63943 @connor4312

Debug Adapter Protocol

• Support additional data fields for breakpoint debug-adapter-protocol#455 @connor4312

API

• Explore improvements to the proposed IssueReporter API vscode#196863 @justschen
• API proposals: query @jrieken @mjbvz
• API finalization: query @jrieken @mjbvz

Extensions

• 🏃 Investigate high extension install error rate vscode#190233 @sandy081
• Update extensions whenever VS Code is about to update vscode#125417 @sandy081
• Support extensions from the workspace vscode#206783 @sandy081

Extension Contributions

• Improvements to the Remote extensions, see plan @roblourens @chrmarti @connor4312 @joyceerhl
• 🏃 Allow resolving merge conflicts without checking out PRs vscode-pull-request-github#5802 @alexr00
• Improve outdated comments experience vscode-pull-request-github#5760 @alexr00
• Improve support for ESLint rules that have inter-file dependencies vscode-eslint#1774 @dbaeumer
• 🏃 Adapt the new ESLint flat config support vscode-eslint#1644 @dbaeumer

Engineering

Electron

• 🏃 V8: Support usage of external array buffers for embedders in sandbox mode chromium#14585 @deepak1556

---

Deferred

• Investigate text-to-speech in panel/inline chat interfaces vscode#196261 @bpasero
• Improve auto indentation in the editor vscode#206891 @aiday-mar @hediet
• Explore better handling of merge conflicts for .ipynb files vscode#160941 @DonJayamanne
• Continue debug visualization exploration vscode#197287 @connor4312
• 💪 Explore Lay-of-the-Land command vscode#201898 @meganrogge
• 🏃 Implemented WASI preview 2 pollables and streams on top of the shared-memory model wasm-wasi#155 @dbaeumer
• 💪 Remove "sortByLabel" default behavior and stale proposed API vscode#73904 @TylerLeonhardt
• 🏃 Allow "Files Changed" in new PR to diff against file on disk vscode-pull-request-github#5163 @alexr00

[gjsjohnmurray]

Disappointment again that neither #59921 nor #73524 are listed, and that @andreamah's only item (#204853) involves polishing a recently-added feature (Quick Search, specifically its Previewing capability) that is still not available (polished or unpolished) to our userbase (pinging @isc-bsaviano) because those two proposed APIs have remained unfinalized for more than 5 years now.

[isc-bsaviano]

As I've explained in the past, our company is migrating from a legacy proprietary IDE to VS Code. That legacy IDE only used virtual file systems, which means that most of our user base will want to continue doing so in VS Code. Users have expressed confusion as to why they must jump through hoops to access these features, and it is certainly a barrier to migration for some. Everyone who has activated the proposed APIs has been happy with them, so from their perspective there is no reason why the APIs can't be finalized. Even if there are minor concerns about them within the VS Code core team, it would be a big boost for end users like us to have the APIs finalized in their current state now, and then have those concerns be addressed through refinement later (like #204853).

[Locwyn42]

#203850
Please, let us select specific GitHub accounts for each extension, many of us dream of having our paid Github Copilot from our personal Github account and the repository management for the work account.

[oenu]

Heads up the

🏃 Improvements to the Remote extensions, see [plan](https://github.com/microsoft/vscode-remote-releases/issues?q=is%3Aissue+label%3Aiteration-plan+milestone%3A%22March+2024%22) @roblourens @chrmarti @connor4312 @joyceerhl

has been a broken link for a while
replace with

https://github.com/microsoft/vscode-remote-release/issues?q=is%3Aissue+label%3Aiteration-plan+milestone%3A%22March+2024%22

....soft/vscode-remote-release<S>/iss... => ....soft/vscode-remote-release/iss...

[sbatten]

Hi @gjsjohnmurray, I appreciate your feedback and also your many contributions to the project over the years. I can understand the frustration of waiting an indeterminate amount of time for a long-standing feature request for which you have personal interest. As you may know, our team members have responsibilities beyond the iteration plan items here and that this comes into play when creating the right balance for each team member's plan. That being said, I am aware of your requests as @joaomoreno has brought them up to me and it is something that @andreamah and I have on our radar and discussed. I ask for your understanding and please remain patient as we look for ways to make progress on those items.

[BartolomeSintes]

"Iteration plan" issues are very useful to know about VSCode short term development. Perhaps comments could be closed to non-collaborators, but why unpin the issue?

[MasterInQuestion]

    Unsure it's situation:
    "workbench.action.compareEditor.swapSides" no-op on "workbench.files.action.compareWithSaved" diff
    https://github.com/microsoft/vscode/issues/204560#issuecomment-1975257379
    .
    But I doubt it merits another issue to needlessly clutter the issue list.

[starball5]

Disappointment again that neither #59921 nor #73524 are listed, and that @andreamah's only item (#204853) involves polishing a recently-added feature (Quick Search, specifically its Previewing capability) that is still not available (polished or unpolished) to our userbase (pinging @isc-bsaviano) because those two proposed APIs have remained unfinalized for more than 5 years now.

@gjsjohnmurray You might be happy to see #209775