Iteration Plan for April 2024

[kieferrm]

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

Endgame

• April 22, 2024: Endgame begins
• April 26, 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

• Accessibility issues, see query @meganrogge team
• Accessibility signal for cell execution progress status vscode#196396 @meganrogge @amunger
• Refine when accessibility signals play in code editor vscode#204257, vscode#205320 @hediet @meganrogge
• Improve handling of inline completion / suggest widget accessibility signals for SR users vscode#208449 @hediet @meganrogge

Workbench

• 🏃 Exploration: Make tree find controls more discoverable vscode#173742 @benibenj
• Improve automatic theme switching behavior vscode#158314 @aeschli

Code Editor

• Explore hover enriching vscode#195394 @aiday-mar @hediet
• 🏃 Improve auto indentation in the editor vscode#206891 @aiday-mar @hediet
  • Skip lines that are part of a multi-line string (or comment) vscode#209859 @aiday-mar @hediet
  • Strip comments from code before evaluating regexes vscode#209861 @aiday-mar @hediet
  • Explore removing brackets from strings before evaluating regexes vscode#209862 @aiday-mar @hediet
• Multi-file diff editor has no TabInput vscode#206411 @lramos15 @hediet
• 🏃 Investigation: Use tree-sitter for grammar colorization vscode#210475 @alexr00
• 💪 Placeholder support vscode#208976 @hediet
• Release the Monaco Editor @hediet

Search

• Polish quick search vscode#209979 @andreamah

Notebook Editor

• 🏃 Filter/grouping support in variables view vscode#208865 @amunger
• Investigate notebook document backup blocking renderer process vscode-jupyter#14459 @amunger
• 🏃 Improving Error Renderer (Default call stack collapse, display '/fix' and '/explain' actions) vscode#200253 @amunger
• 🏃 Explore API to support notebook document formatting with Ruff and Black vscode#207334 @Yoyokrazy @rebornix
• 🏃 Investigate freeze/slowness on notebook cell execution vscode#209787 @DonJayamanne

Jupyter Notebooks

• Roll out experiments for dropping "custom" namespace in cell metadata and api migration in codespace extension vscode#205637 @DonJayamanne
• Deprecation notice for the Data Viewer in Jupyter vscode-jupyter @rebornix @amunger

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 vscode#203247 @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
• Use vscode watches for tsserver vscode#193848 @bpasero

Terminal

• 🏃 Expose shell integration command knowledge to extensions vscode#145234 @Tyriar
• 💪 Explore Terminal Buffer access for extensions vscode#207504 @Tyriar
• Terminal middle click paste option vscode#187365 @Tyriar

Source Control

• 🏃 Working sets for git branches vscode#35307 @lszomoru @bpasero

Testing

• Finalize test coverage API vscode#123713 @connor4312
• Support preserveFocus on test runs vscode#209491 @connor4312

Debug

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

API

• 🏃 Explore finalizing FileSearchProvider API vscode#73524 @andreamah
• 🏃 Explore finalizing TextSearchProvider API vscode#59921 @andreamah
• API proposals: query @jrieken @mjbvz
• API finalization: query @jrieken @mjbvz

Extensions

• 🏃 Investigate high extension install error rate vscode#190233 @sandy081
• Create GitHub releases whenever releasing vsce vscode-vsce#862 @benibenj
• Support the files property in package.json vscode-vsce#867 @benibenj
• Finalize support local workspace extensions 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
• 🏃 Adapt the new ESLint flat config support vscode-eslint#1644 @dbaeumer

Electron

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

---

Deferred

• Support Find in editor selection, selected cells, or sections in Notebook Find Widget vscode#209839 @Yoyokrazy
• Explore better handling of merge conflicts for .ipynb files vscode#160941 @DonJayamanne
• 💪 🔴 Explore updating extension template to use esbuild @aeschli
• Investigate text-to-speech in panel/inline chat interfaces vscode#196261 @bpasero

[umpox]

Hi!

I'd love to see some progress on some proposed features that have been around for a while, I know there's a lot of extensions that would make great use of these features:

• SourceControl - scm/inputBox menu contribution proposal #195474
  • This was available previously but was disabled, a number of extensions were making use of this (inc GitLens). It'd be great to support this again!
• https://github.com/microsoft/vscode/blob/main/src/vscode-dts/vscode.proposed.codeActionAI.d.ts (I didn't see any issue for this, shall I make one?)
  • This is a small boolean addition that has been proposed for 7 months. Lots of other extensions would make great use of this category for AI fixes.

Please let me know if I can help in any way. Thank you!