Closed
Description
openedon Feb 9, 2019
This plan captures our work in February. This is a 4 week iteration, and we will ship our February Update in in early March. We'll continue work we started in the previous iteration, and we started to pick up items from our roadmap.
Endgame
- February 25, 2019: Code freeze for the endgame (Zurich freezes on February 22)
- March 1, 2019: Endgame done
The endgame details for this iteration are tracked in #69177.
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
- Revisit the custom menubar on Linux Do not use CSD by default on Linux #65608 @sbatten
- Simplify switching to an newly installed theme Improve user experience while installing themes #68408 @sandy081 @aeschli
- Adopt new tree in Outline Adopt Object tree for outline and breadcrumbs #64727 @jrieken @joaomoreno
UX
- 🏃 Iconography re-design Inconsistent weight and use of color in iconography throughout UI #8017 @misolori
Editor
- Improve hover presentation for complex errors Improve hover presentation for complex errors #67076 @sandy081
- Adopt new tree in bread crumb Adopt Object tree for outline and breadcrumbs #64727 @jrieken @joaomoreno
Tasks
- 🏃 Add support for custom execution in addition to ShellExecution and ProcessExecution Allow extension to provide callback functions as tasks #66818 @alexr00
Languages
- 🏃 Support semantic selections Expand selection functionality issues #4795 @jrieken
LSP
- Support semantic selections Feature request: "document/extendSelection" for semantic selection language-server-protocol#613 @dbaeumer
- 🏃 PR #426 LSP support for type hierarchies @dbaeumer
- 🏃 PR #420 LSP support for call hierarchies @dbaeumer
- 🏃 PR #261 LSP support for progress reporting @dbaeumer
JavaScript/TypeScript
- Adopt TypeScript 3.3.x Bundle TypeScript 3.3.x #68823 @mjbvz
CSS/HTML
- Update CSS and HTML language services with MDN data Make HTML Language Service data driven vscode-html-languageservice#44 @octref
Debug
- Support a "debug target ready" hook for launch configs Support a "debug target ready" hook for launch configs #69311 @weinand
- Explore how to support extending the debug toolbar Allow customisation of debug toolbar (eg. additional buttons) #45116 @isidorn
- 🏃 Providing additional hooks for generating
launch.json
Provide extension hooks to generate debugger configuration when clicking Add Configuration button #65988 @isidorn - Investigate Find in Console Debug Console should support find #4338 @isidorn
Debug Adapter Protocol
- Finalize data breakpoints Data breakpoints proposal debug-adapter-protocol#20 @weinand
- Investigate protocol addition to support opening a page in the browser Debug protocol: Support browser launching debug-adapter-protocol#23 @weinand
Extension Contributions
- Work with extension authors on adoption of dynamic loading of extensions Allow third party extension points to be marked with
isDynamic
#67958 @sandy081 @alexandrudima - Migrate
vscode-tslint
to use tslint as a TS server plugin Todo typescript-tslint-plugin#1 @mjbvz @egamma - Contributions to the GitHub PR extension Plan for February 2019 vscode-pull-request-github#921 @rebornix @RMacfarlane
- Contributions to the Vetur extension https://github.com/vuejs/vetur/milestone/5 @octref
Extensions
- Webpack eslint extension @dbaeumer
API
- API finalization: query
- API proposals: query
- Reconsider comment provider APIs Comments API refactor #68020 @rebornix @RMacfarlane @jrieken
Exploration
- 🏃 Explore support for developing on WSL Explore support for developing on WSL #63155 @alexandrudima team
- 🏃 Explore supporting Electron 5.0 default renderer configuration Explore supporting Electron 5.0 default renderer configuration #68302 @bpasero @sbatten
- Explore webview rendered code insets Code inset feature #66418 @jrieken
Engineering
- Ensure user need to choose target when filing issues Issue reporter: force reporter of an issue to make a choice whether the issue is for VS Code or an extension #66080 @RMacfarlane
- Ensure all of our built-in extensions support dynamic loading Make markdown extension points dynamic #67574 Make the typescript plugins extension point dynamic #67575 @mjbvz team
- 🏃 Strict null checking VS Code Strict null checking VS Code #60565 @mjbvz team
- Compile TS to ES6 Compile to ES6 #65372 @jrieken
Documentation
- Revisit Javascript end user documentation Explore reorganizing js/ts docs vscode-docs#2190 @mjbvz @gregvanl
- 🏃 Create a guide for webpacking extensions bundle extension using webpack #64532, add webpack topic vscode-docs#2403, Recommend bundling extension vscode-vsce#333 @jrieken
Deferred Items
- Explore flatting folder hierarchies in the explorer Explorer: Support compact folder rendering #41627 @isidorn @joaomoreno
- ✋ Electron 4.0 upgrade Explore update to Electron 4 #61787 @bpasero
- Explore alternative extension install/management experiences Explore Extensions Management UX #68527 @misolori @sandy081
- Improve presentation of debugged subprocesses Display debugged sub-processes as a treeview #62972 @weinand
- Investigate reviving translations for the Monaco editor @dbaeumer
- Improve user experience when multiple-formatters are registered Make it clear what happens when multiple formatters for one document apply #41882 @jrieken @octref