Iteration Plan for November 2018

[kieferrm]

This plan captures our work in November. This is a 5-week iteration. We will ship our November Update - the last of the year - in the first half of December. As in 2018, there will be no update in early January 2019. The next major update will be in early February 2019.

We have a full plan stretching from polishing functionality that we introduced earlier such as reference lists and multi-line search, to smaller productivity features such as Commit & Push, all the way to getting ready for electron 3.0 and adopting the new tree implementation throughout our code base. We also start exploring what it takes to make developing on WSL on Windows more natural. Some of us will also eat a lot in the middle of the iteration.

Endgame

• December 3, 2018: Code freeze for the endgame
• December 7, 2018: Endgame done

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

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

Workbench

• 🏃 Explore flexible panel/sidebar layout Investigate to rewrite workbench layout using grid widget #50853 @sbatten @joaomoreno
• Polish viewlet that shows search reference results make finding all references more user-friendly #22261 @jrieken
• Improve multiline search experience Allow multiline search to be enabled without regex #62304, Multiline search widget #62961 @roblourens
• Support overflow in custom menubar and menus Context menus do not overflow #52533 No menu overflow causes problems with narrow windows/long titles #57756 @sbatten
• Enable custom menubar on Linux by default Switch to custom menus in Linux by default #62727 @sbatten
• Improve rendering of diagnostics in hovers and F8 Error hover semantic information should be rendered separate of error message #62370 @sandy081
• Explore deprecating the old settings editor Consider deprecating the split JSON settings editor #62964 @roblourens

UX

• Explore streamlining design for hovers, completion items, signature help Explore improving UX for IntelliSense #63144 @misolori
• Explore welcome page improvements Explore improving UX for Welcome Page #63152 @misolori

Monaco Editor

• Publish a new editor version @alexandrudima

Tasks

• Support input parameters for Tasks Task Runner: Provide input parameters #4758 @alexr00
• Support to start a task automatically Auto start watch task #17147 @alexr00
• Explore to automatically attach problem matcher when running in the terminal Explore improving attach problem matcher UX #62937 @alexr00

Source Control

• Support one-step action Commit & Push Add git autopush option when committing (revisited) #62058 @joaomoreno
• Provide option to open file on single click from SCM viewlet Git: Support to open file on click, by default #63005 @joaomoreno

Languages

• 🏃 Improve expand selection support Expand selection functionality issues #4795 @jrieken
• Add "Go to Declaration" feature Add support for Goto Declaration #62483 @jrieken
• Add go-to-declaration request to LSP Add support for Goto declaration language-server-protocol#605 @dbaeumer

JavaScript/TypeScript

• Adopt TS version 3.2 @mjbvz Bundle TypeScript 3.2 #63179
• Allow VS Code extensions to configure TS Server plugins Allow vscode extensions to configure TS Server plugins #63181

CSS/HTML

• 🏃 Support custom tags and properties in HTML and CSS Web Components support in HTML files #62976 @octref

Debug

• Loaded Scripts view improvements (observing changes, explore filtering based on new tree) Loaded Scripts view improvements (new Tree widget, observing changes, filtering) #62939 @weinand
• Polish multi-debug console support Need launch config option to disable multiple debug consoles #62419 Debug consoles cannot be deleted #62418 multi debug console feature is not aligned with integrated and external terminals #62420 @isidorn
• Explore supporting data break points Possibility to add data breakpoints #58304 @weinand
• Explore minimal multi-step quick pick providing guidance for creating launch configs Leaner launch.json generation #62851 @isidorn
• Investigate issues with debugging apps generated with create-react-app Debugger Won't hit breakpoints in jest test #60187 @roblourens
• Enable Smart Step by default Enable smartStep by default for node debugging #62965 @roblourens

Extension Contributions

• 🏃 Migrate vscode-tslint to use tslint as a TS server plugin Todo typescript-tslint-plugin#1 @mjbvz
• GitHub PR extension Plan for November 2018 vscode-pull-request-github#678 @rebornix @RMacfarlane

Extensions

• Support installing the previous version of an extension Ability to install older extension #12764 @sandy081

API

• Help extensions moving off the htmlPreview Deprecating previewHtml #62630 command @mjbvz
• Explore alternatives to FileIndexProvider Remove/evolve FileIndexProvider #59922 @roblourens
• API finalization: query
• API proposals: query

Serviceability

• Identify extensions causing the extension host to be unresponsive, provide support for generating a CPU profile, hint user about the performance problem caused by the extension. Profile extension host when needed #60332 @jrieken
• Support to start debugging directly from within the process explorer Allow to debug process right from the Process Explorer #63147 @RMacfarlane

Exploration

• 🏃 Explore support for developing on WSL Explore support for developing on WSL #63155 @alexandrudima team

Engineering

• Continue Electron 3.0 adoption, migrate local storage Explore update to Electron 3 #52629 @bpasero
• WinJS.Promise removal WinJS.Promise removal plan #53526 @jrieken team
• 🏃 Strict null checking VS Code Strict null checking VS Code #60565 @mjbvz team
• Document new Tree widget implementation (https://github.com/Microsoft/vscode/wiki/Lists-And-Trees) @joaomoreno
• Support the adoption of the new Tree widget @joaomoreno
  • 🏃 Adopt new tree widget in Search @roblourens
  • 🏃 Adopt new tree widget in Settings @roblourens
  • Adopt new tree in peek references ui @jrieken Adopt data tree for references peek view #63904
  • Adopt new tree widget Outline @jrieken
  • 🏃 Adopt new tree widget in the debugger @isidorn, @weinand

Documentation

• 🏃 Continue extensibility documentation improvements Plan to continue polish extension doc vscode-docs#2199 @octref team

---

Deferred Items

• Revisit the explorer context menu (cut, duplicate, open folder) Please add the file/folder cut command to the context menu and the releated shortcut. #61110 @isidorn @bpasero
• 💪 Explore flatting folder hierarchies in the explorer Explorer: Support compact folder rendering #41627 @isidorn @joaomoreno
• Explore Debug API: Debug Config Provider to return launch configurations dynamically Debug Provider to return launch configurations 'in-memory' to the debugger #54212 @weinand
• Adopt new tree widget in the workbench @isidorn
• Support a post install/update hook for extensions Support Platform Specific Extensions #23251 @sandy081 @joaomoreno
• Explore generalizing NPM Script Explorer into a Task runner view Provide Task Runner viewlet #28235 @alexr00
• 💪 Use browser logic for improved word navigation in CJK Feature request: Treat the Chinese text as a Chinese sequence when usingCtrl+Left/Right #50045 @rebornix
• Explore impact of Webview changes in electron 3.0 on extensions @mjbvz Test webview extensions on electron 3.0 #63180
• 💪 Revisit Javascript end user documentation @mjbvz @gregvanl Explore reorganizing js/ts docs vscode-docs#2190

[chpxu]

Explore welcome page improvements #56144

[BartolomeSintes]

Please, don't remove the old settings editor (last item in the workbench section of this month's plan). It is easier to copy and paste all the settings at once (from one workspace to another) than modify one by one.

[roblourens]

We will never get rid of editing settings with a JSON file. The issue is just about the UX we have around the json settings editor (pencil icon to edit, search bar, etc).

[vSanjo]

The search bar is a little annoying in settings.json view. I'd rather be looking through my settings I've set over the settings I have available. Perhaps a toggle between the two?

[jtcontreras90]

CSS/HTML
- [ ] Support **support** for custom tags and properties in HTML and CSS #62976 @octref

[myfairsyer]

There's an issue for the endgame: #64182

[kieferrm]

Shipped.