Iteration Plan for November 2020

[kieferrm]

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

We've spent the first two weeks of this iteration finishing our annual housekeeping. You can see the progress me made on https://vscode-github-stats.netlify.app/ that @lannonbr created for us a while back. If you are interested in why we have issue house keeping iterations and in our general philosophy around issue management, then we have this write-up for you.

Because of house keeping, the plan items below are mostly for the second half of the iteration. You might feel that you see more muscle items than usual. That is not an illusion. Since we don't ship a release in early January, we don't have a December place. The work in December is captured in our muscle items and will carry over into our January plan.

Endgame

• November 30, 2020: Endgame begins
• December 4, 2020: Endgame done

The endgame details for this iteration are tracked in #111406.

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

Housekeeping

• Issue/PR Grooming - review, categorization, assignment 2020 Issue Grooming - review, categorization, assignment #108472 team

Accessibility

• Accessibility issues, see query team
• 🏃 Assess notebook accessibility VS Code native notebook accessibility improvement #111255 @isidorn @rebornix @roblourens

Workbench

• 🏃 💪 Explore the concept of Trusted Workspaces General Discussion on Workspace Trust Feature #106488 @lszomoru @sbatten
• 🏃 💪 Investigate predefined file filters search (Investigate predefined file filters search #106790) @JacksonKearl
• 🏃 💪 Explore support for adding/organizing imports on Paste Add events for copy/paste to allow language extensions to bring using/import statements along #30066 @mjbvz
• 🏃 💪 Improve the welcome pages Explore improvements to welcome pages #106715 @misolori @JacksonKearl
• ✋ Improve emmet support Migrate to the latest Emmet #110697 @rzhao271
• 💪 Explore showing file decorations in editor tabs Decorations: Show decorations in tabs #49382 @jrieken
• Improve initial appearance of Welcome Views in the explorer API: Add enablement to welcome view buttons #106487 @joaomoreno
• 🏃 Supporting to customize the product icons [themes] Add product icon themes #92791 @aeschli @misolori
• Add sorting support for the Open Editors list Add sorting to Open Editors list #12453 @isidorn
• Support undo/redo of explorer operations Undo of rename Java file has no effect #107740 @isidorn
• Improve our handling of process environment depending on context Do not wait for shell environment resolution before opening window #108804 @bpasero @joaomoreno

Notebook Editor

• Scale to large simple outputs Large text output kills the notebook #110581 @rebornix
• Address notebook papercuts Notebooks: Self-hosting experience #109549 @rebornix @roblourens @misolori
• Introduce metadata to control rendering of outputs Trust Notebook Content and readonly notebooks #108946 @rebornix
• Support to not render empty outputs Add ability to hide outputs in Notebooks #109104 @rebornix
• ✋ Identify and fill API gaps for Live Share API gaps to support Liveshare in Notebook #102503 @rebornix
• 🏃 Explore notebook keymap support Explore notebook keymap support #106679 @rebornix @roblourens
• 💪 Explore extensible markdown rendering for notebooks Explore customizing the markdown renderer for notebooks #106701 @mjbvz
• 💪 Improve notebook diff editor scrolling performance Scrolling in a notebook diff editor is sluggish #109680 @rebornix
• 💪 Explore output renderer support in notebook diff editors https://github.com/microsoft/vscode/issues?q=is%3Aopen+label%3Anotebook+diff @rebornix
• 💪 Explore options to support free-floating output renderer elements Notebooks - HTML elements (widgets) in output overflow & get displayed under the editor #108947 @rebornix
• 💪 Explore options to allow an output to go into full-screen mode Allow an output to go into full-screen mode #110766 @rebornix

Editor

• Support word wrap in the diff editor Support word wrap in the diff editor #11387 @alexdima

Languages

LSP /LSIF

• LSP - version 3.16 including features like (onTypeRename, onDid*, onWill* events) @dbaeumer
• LSIF - Same source for multiple projects support Support source files being part of multiple TS projects lsif-node#116 @dbaeumer
• 💪 LSP - investigate supporting a pull model for diagnostics (diagnostics are currently delivered using a push model) Add support for explicitly requesting diagnostics language-server-protocol#737 @dbaeumer

JavaScript/TypeScript

• Adopt TS 4.1 Pick up final release of TS 4.1 #111000 @mjbvz
• Improve TypeScript version selector Add clearer indicator of current version to TS version selector #111001 @mjbvz

Debug

• 💪 Update all node debug documentation/tutorials to use debug-js Update JavaScript debugger user doc for js-debug vscode-docs#4123 @connor4312
• Collapse identical lines in the debug console Collapse identical lines in the debug console #104162 @isidorn
• Improve the dynamic launch config UI https://github.com/microsoft/vscode-docs/issues/110009 @isidorn
• 🏃 Improve stack traces for extension debugging Call native logging APIs when debugging in the extension host #104686 @connor4312 @isidorn
• Show help text/tip at the bottom of debug hover to switch to the language hover Show the help text/tip in the bottom of debug hover to switch to normal hover #107697 @isidorn
• Add condition editing UI for exception breakpoints Add condition editing UI to breakpoint filters #111227 @isidorn
• 🏃 improve "inline values" https://github.com/microsoft/vscode-docs/issues/101797 @weinand
• ✋ Improve the "breakpoint hit" UI for Web UI Improving stopped indication ("breakpoint hit") for Web UI #100757 @weinand @isidorn

DAP

• Support conditions for exception breakpoints Proposal: allow conditional exception breakpoints debug-adapter-protocol#137 @weinand
• Investigate: Is StackTraceResponse.totalFrames truly necessary? [debug] Is StackTraceResponse.totalFrames truly necessary? #31851 @weinand
• Review: Support object favorites Proposal: Support object favorites debug-adapter-protocol#132 @weinand
• 🏃 Continue discussion: Support object IDs Proposal: Support object IDs debug-adapter-protocol#134 @weinand
• 🏃 Investigate: control escaping/quoting arguments for the runInTerminal request add property for controlling escaping arguments for the runInTerminal request debug-adapter-protocol#146 @weinand

Testing

• 🏃 Explore how to improve testing support Testing in VS Code #107467 @connor4312 @sandy081

Terminal

• Explore ways to inform users about the specifics of terminal keyboard shortcuts Prompt user with info about terminal config, add settings search by @id, and add sendToShell setting #110987 @meganrogge
• 🏃 💪 Restore terminal UI state Terminal: remember layout between restarts #109244 @roblourens @meganrogge

Source Control

• Guide users if user.name or user.email are undefined in git config Guide users to set user.name and/or user.email if missing from git config #110880 @eamodio
• 🏃 Warn when pushing to a rebased branch Warn before pulling if a branch appears to have been rebased #110881 @eamodio
• Git: Support optional branch picking in the repository picker Git: Support optional branch picking in the repository picker #106664 @joaomoreno
• 💪 Guide user to push to a remote after creating a commit Explore UI additions to help guide users to push to a remote after committing #110882 @eamodio

API

• API finalization: query
• API proposals: query

Extensions

• Support to bisect extensions to narrow down a malfunctioning extension @jrieken
• 💪 🔴 Explore bracket pair colorizing performance improvements @alexdima

Extension Contributions

• Improvements to the Remote extensions Remote: Iteration Plan for November 2020 vscode-remote-release#4017 team
• 💪 Improvements to the GitHub PR extension Improvements to the PR flow vscode-pull-request-github#2293 @RMacfarlane @eamodio

Install

• 💪 🏃 Explore installing the Remote-WSL extension out of the box on Windows Investigation: Installing a WSL extension out of the box on Windows #106759 @joaomoreno @aeschli

Engineering

• ✋ Publish Linux ARM deb, rpm and snap to repositories Publish Linux ARM deb & rpm repositories #106473 @joaomoreno
• 🏃 Make VSCode Trusted Types compliant Trusted Types compatibility: Make VSCode TrustedTypes compliant #103699 @jrieken and team
• 🏃 Stabilize Apple Silicon builds Stablize apple silicon exploration builds #106770 @deepak1556
• 🏃 electron 11 adoption chore: update to electron 11 #110759 @deepak1556
• Adopt vscode.open and vscode.diff in SCM, Timeline, GHPRI extension
  • SCM/git @joaomoreno
  • Timeline @eamodio
  • GHPRI extension @alexr00

Node.js-free, sandboxed renderer

• 🏃 Backlog Implement a node.js-free, sandboxed, context isolated renderer  #92164 @bpasero @deepak1556

---

Deferred Items

• 🏃 Explore possible integrations between extensions view and GH Sponsors Explore integration between extensions view and GitHub Sponsors #107482 @misolori

[sandstrom]

Any chance you could add this feature to your November or December plan? 🎄 🎁

Allow to change the font size and font of the workbench — #519

It's got 1600 up votes, 270 comments (second most) and it's five years old.

[MatthewS2077]

Allow to change the font size and font of the workbench — #519

Yes please! 🙏 We shouldn't need to resort to "Monkey Patch" to change our font.

[ssbarnea]

Not sure how "Extension Bisect" was implemented but it seams to be missing from macos Version: 1.52.1 version of vscode. There is no option to be found anywhere about it.

[alexdima]

@ssbarnea You can find it by pressing F1 and picking Help: Start Extension Bisect

[ssbarnea]

Now I feel stupid: I used the Help menu, which does not have such an option but it has a search, a search that finds nothing when typing bisect.

Please take a look at https://code.visualstudio.com/updates/v1_52#_troubleshooting-extension-bisect and you will soon realize why the blog post is confusing.

Do you see how "Help" is advertised... the other help. Probably it would have being less confusing to replace the text with "F1 > .." instead of "help".

[alexdima]

cc @gregvanl @jrieken re #110690 (comment)

[gregvanl]

Fixed release notes to use correct Command Palette name for Extension Bisect commands microsoft/vscode-docs@ea9c64c