Iteration Plan for May 2022

[kieferrm]

This plan captures our work in May. This is a 5-week iteration. We have several holidays across countries coming up which gives us a bit less than 5 weeks of work time. We will ship in early June.

Endgame

• May 30, 2022: Endgame begins
• June 3, 2022: 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 @isidorn team

UX

• 🏃 Explore improving the discoverability of filtering in tree views vscode#146806 @misolori @joaomoreno
• Improve extension UX guidelines vscode-docs#5327 @daviddossett
• Explore improvements to custom menu styles vscode#148587 @daviddossett
• Explore more visible section headers in quick pick lists vscode#149057 @daviddossett
• 💪 Indicate focused tab when using multiple editor groups in HC themes vscode#145563 @daviddossett

Workbench

• 🏃 Explore profile management vscode#116740 @sana-ajani @sandy081 @daviddossett
• 🏃 Explore Continue On... support in core vscode#141293 @joyceerhl
• 🏃 Explore a Share as... menu for creating vscode.dev links vscode#146309 @alexr00
• Problems view - support rendering as a table vscode#98819 @lszomoru
• 🏃 💪 Adopt inline suggestions for previewing emmet expansions vscode#139247 @rzhao271 @hediet
• Investigate use of .gitignore to filter content in the Explorer vscode#38878 @lramos15 @JacksonKearl
• ✋ Adopt Window Control Overlay API in electron 18 vscode#147947 @sbatten
• Explore Command Palette launcher in titlebar vscode#149445 @jrieken
• Investigate global policy support vscode#147756 @joaomoreno
  • Generate Windows Group Policy definition files from static analysis vscode#148941 @joaomoreno
  • Create a PolicyService and use it in the ConfigurationService vscode#148943 @joaomoreno @sandy081
  • Surface policy values in settings editor vscode#148944 @rzhao271
• 🏃 Settings Editor: Indicate if setting has a language-specific value vscode#145731 @rzhao271 @sandy081
• 💪 Explore reuseable inline edit widget for tree views vscode#149641 @lramos15

Web

• 🏃 Explore translations in the web vscode#82595 @TylerLeonhardt
• Support workspace trust in the web vscode#145564 @sbatten
• 🏃 Explore how a web extension can leverage the WebUSB API vscode#116761 @mjbvz @alexdima
• 🏃 Explore a partial WASI implementation using the VS Code API vscode#149092 @dbaeumer

Code Editor

• Explore the implementation of a merge editor vscode#146091 @hediet @jrieken
• 💪 Explore moving tokenization to a web worker vscode#147066 @hediet
• 💪 Align editor find widget with the notebook find widget vscode#144851 @rebornix

Notebook Editor

• Tune autoselection of controllers vscode#146339 @rebornix
• Provide support for proxy controllers vscode#146942 @rebornix @misolori
• 🏃 Improve notebook “scrolling up” rendering performance vscode#148164 @roblourens
• Improve cell positioning when using the Outline view vscode#123828 @roblourens
• Improve cell positioning when using arrow keys across cell boundaries vscode#147527 @roblourens
• Explore allowing extensions to manage cell context keys vscode#146686 @roblourens
• 🏃 Explore improving files search results for notebooks vscode#95275 @roblourens
• Improve notebook language detection CPU performance vscode#148762 @JacksonKearl
• 💪 Allow resizing for the find widget in notebooks vscode#141516 @rebornix
• 💪 Support copying simple output to the clipboard vscode#129880 @amunger @rebornix
• 💪 Show changes in the overview ruler of the notebook diff editor vscode#146224 @amunger @rebornix

Jupyter Notebooks

• Contributions to the vscode-jupyter extension vscode-jupyter#9937 @greazer team

Languages

AnyCode

• Limit AnyCode providers when rich language extension is present anycode#38 @jrieken
• Build index for a language only when there is strong evidence that an index is necessary anycode#39 @jrieken

Python

• Contributions to the python extension vscode-python#19088 @brettcannon team

JavaScript/TypeScript

• ✋ Support TS server plugins on web vscode#140455 @mjbvz
• ✋ Support TS project-wide intellisense on web typescript#47600 @mjbvz
• ✋ Explore automatic type acqusition on web typescript#45314 @mjbvz

Markdown

• 🏃 Investigate create file and image links using DnD vscode#142990 @mjbvz
• 🏃 Explore pasting images into markdown (file url, data url) vscode#119961 @mjbvz

CSS

• Adopt LSP pull diagnostics in CSS vscode#149643 @aeschli

JSON

• Support unevaluatedProperties for JSON schemas vscode-json-languageservice#132 @aeschli
• Adopt LSP pull diagnostics in JSON vscode#149643 @aeschli
• 💪 Explore test suite from JSON schema spec vscode-json-languageservice#120 @aeschli

Debug

• Support showing diagnostic information in the breakpoints view vscode#142870 @roblourens @weinand @connor4312
• Explore avoiding the "Select environment" prompt when launching a debugger without launch.json vscode#146338 @roblourens @weinand
• 🏃 Remove special treatment of extension debugging in VS Code (Prototype extension debugging in a clean environment) vscode#126737 @weinand

js-debug

• 🏃 💪 Investigate: Smart Step Into vscode#123879 @connor4312 @weinand
• Investigate supporting to attach to webviews running inside UWP applications vscode-js-debug#1209 @connor4312

Testing

• 🏃 💪 Provide support for Go to Test/Go to Test Subject vscode#126932 @connor4312

Terminal

• Render find matches on the background layer vscode#147013 @Tyriar @meganrogge
• Optimize decorations performance in the terminal vscode#145751 @Tyriar @meganrogge
• Improve prompt response time when shell integration is enabled vscode#145576 @meganrogge @Tyriar
• Improve shell integration user experience vscode#148856 @meganrogge

Tasks

• 🏃 Change feature area ownership of tasks vscode#149060 @meganrogge @Tyriar @alexr00

Source Control

• Git logging improvements vscode#148656 @lszomoru
• Add support for random branch name generation vscode#148781 @lszomoru
• Support to configure branches which should be protected from direct commits vscode#148783 @lszomoru

API

• API finalization: query @jrieken @mjbvz
• API proposals: query @jrieken @mjbvz
• 🏃 Continue finalization of remaining proposed notebook API vscode#149861) @mjbvz @rebornix @roblourens

Extensions

• Support an activation event for timeline view vscode#94151 @lramos15 @JacksonKearl
• Deprecated extensions support vscode#4772 @sandy081
• Show Sponsor information for extension authors vscode#107482 @sandy081

Extension Contributions

• GitHub Repositories: query @joyceerhl
• Improvements to the Remote extensions vscode-remote-release#6699 @tanhakabir @chrmarti @aeschli
• GHPR: Improvements papercuts, selfhosting issues, query @alexr00
• 💪 Investigate eslint notebook support in the web vscode-eslint#1366 @dbaeumer

Install

• 🏃 Integrate with the Windows 11 explorer context menu vscode#127365 @deepak1556

Engineering

• Explore new Electron process utility for spawning the extension host vscode#131798 vscode#135268 @alexdima @deepak1556
• Provide a translation build for our extensions; onboard the Python extension and other extensions vscode#150202 @TylerLeonhardt @paulacamargo25

Electron

• 🏃 Improve dependency generation for Debian vscode#13089 @rzhao271
• 🏃 Update requestSingleInstanceLock API to use MessageWindow for acknowledgement electron/electron#34235 @rzhao271
• Explore Electron 18 update vscode#145527 @deepak1556

Documentation

• 🏃 Improve TS docs vscode-docs#5205 @gregvanl @isidorn

---

Deferred

• A full editor can be used as git commit message editor vscode#30562 @lszomoru
• Investigate grouping of events in timeline view vscode#145294 @JacksonKearl @lramos15
• Context menu on the minimap to hide/show it vscode#148131 @alexdima
• Investigate providing a default snippet for a language vscode#145929 @jrieken @digitarald
• 🔴 Explore improve first-run experience for running a Jupyter notebook @misolori
• Make the eslint extension more approachable for new contributors vscode-eslint#1447 @dbaeumer
• Review errors to identify which ones are actionable as error telemetry vscode#145043 @lramos15 team
• Draft Git Beginner's Docs vscode-docs#5033 @digitarald @burkeholland
• Implement a node.js-free, sandboxed, context isolated renderer vscode#92164
• Enable contextIsolation for all windows vscode#128099 @bpasero @rzhao271 @deepak1556
• Fix cursor for draggable region elements on macOS vscode#140724 @rzhao271
• Refactor startup code to use electron's requestSingleInstanceLock API vscode#97626 @rzhao271
• Explore variable line heights in the editor vscode#147067 @hediet
• Improve presentation of inline suggestions with imprecise prefix matches vscode#147068 @hediet @misolori
• Explore a view header menu contribution point in the Explorer vscode#108271 @JacksonKearl
• Issue reporter template - include versions of built-in extensions that have been updated vscode#145529 @sandy081
• Consolidate notebook setting names vscode#142986 @rebornix @roblourens
• Improve cell level commenting in notebooks vscode#144850 @rebornix
• Review and update Integrated Terminal vscode-docs#4809 @gregvanl @Tyriar

[fisforfaheem]

Updating to latest ELECTRON version will also fix so many performance issues found in electron

[lorand-horvath]

Updating to latest ELECTRON version will also fix so many performance issues found in electron

Do you mean from 17.4.1 to 17.4.3 (I've opened issue #149223) or the newer 18.x branch? https://github.com/electron/electron/releases/tag/v18.2.2

I should mention the slowness and lag reported in #146737 which nobody seems to care about (ticket closed, merged with other issues, etc) - the problems have been obviously introduced with Electron 17 since VSCode 1.66

[praveer-k]

Any plan to include a toggle button to show/hide code section. Make it look like a report instead of showing code in jupyter notebook?

[vhscom]

Do you mean from 17.4.1 to 17.4.3 (I've opened issue #149223) or the newer 18.x branch?

Anything you can do to improve performance at this point would trump any more features in my perspective. I used to sing praises for VSCode telling people it didn't feel like Electron. Today, however, I would tell them it feels like an Electron app unless you're using bleeding edge hardware. A code editor should not heat up a 2019 MBP.

@lorand-horvath I saw you added a confused emoji. Was there something in my feedback that confused you?