Iteration Plan for July 2018

[egamma]

This plan captures our work in July. This is a 5-week iteration. We will ship our July Update in early August.

Being in the Northerm Hemisphere, July is the first of our two Summer iterations that traditionally are a little bit lighter than the rest of the year. Many of us are out for a couple of weeks hanging out on beaches, climbing mountains, riding bikes, sleeping in the sun. We surely hope you will too.

Nevertheless, work will be done. In June we made good progress moving features out of preview. We are optimistic we can do the same for the alternative settings UI in July. We will make a user setup on Windows available, which does not require Administrator privileges to install. This setup package will provide a smoother background update experience on Windows. We also try to push the extension for GitHub pull requests so far that it's worthwhile to publish a preview in the extension marketplace.

We'll also use the Summer to look into improving accessibility of VS Code (keyboard navigation, screen reader support etc.) and make overall issue reduction a focus. The latter you already know from previous iterations. Having many actively engaged users on GH means high issue traffic and we always have to walk the delicate balance between being responsive to issues and getting sufficient focus time to get things done.

Endgame

• July 30th, 2018: Code freeze for the endgame
• August 3rd, 2018: Endgame done

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

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

Accessibility

• 🏃 Fix accessibility issues See query. @isidorn @ramya-rao-a team

Workbench

• 🏃 Continue to improve settings experience Provide GUI for settings #3355 @roblourens
  • 🏃 Explore settings editor improvements possible with additional metadata Explore extending settings schema with additional metadata #51778 @roblourens @misolori
  • Support rendering of backticks and links @roblourens Render setting descriptions as markdown #53911
  • Improve files.exclude control @roblourens @misolori Explore files.exclude control for the new settings editor #53913
• 🏃 Polish custom titlebar and menus on Windows (titlebar query) (menus query) @sbatten
• Improve global menu structure, e.g. the View menu @bpasero @misolori
• Support to open a workspace from a URI Support opening folders with other schemes #54483 @sandy081 @aeschli
• 'bread-crumb' navigation Feature Request : Navigation Bar like Visual Studio or Eclipse #9418 @jrieken @misolori
• Introduce a log file all telemetry events Log telemetry events into separate log file and the output channels for logs #54001 @ramya-rao-a
• Simplify entering offline mode Offline mode for VS Code #54354 @ramya-rao-a
• Explore how to support multi-line searches and search results @roblourens @misolori Support multi-line search for Global search #13155
• ✋ 🏃 💪 In Settings search, provide a way to show matching but not-installed extensions Show settings search matches from non-installed extensions #49474 @roblourens

Terminal

• Keep renderer process in sync with pty @Tyriar Terminal output can block the renderer process #42234 Test if we can pull terminalProcess into the renderer process #53974

Install

• Make user level install available; guide users to user level install @joaomoreno

Problems Panel

• Support quick fixing a problem from the Problems Panel Allow triggering quick fixes from problems view #52627 @sandy081

Languages

Language Server Protocol

• Support hierarchical document symbols vscode-languageserver-node#3739 @dbaeumer
• Support the preselect property for completion items 515 @dbaeumer
• Improve LSP inspector query @octref
• Publish language aware folding support [folding] add language aware folding to LSP #45983 @aeschli
• Explore improved support for language extension tests
  Add a testing section to Language Server Guide octref/vscode-language-server-e2e-test#2 Expand the sample to cover all language features octref/vscode-language-server-e2e-test#3 @octref

JavaScript/TypeScript

• Adopt TS version 3.0 Adopt TypeScript 3.0 #54845 @mjbvz
• As part of TS 3.0
  • Support for auto closing JSX tags Auto close JSX tags. #34307 @mjbvz
  • Support for Typescript project references Tooling support for TypeScript project references #54104 @mjbvz
  • Support for TS multi-location diagnostics Support diagnostics references from TypeScript  #54102 @mjbvz
  • Update third party notice. See here Update typescript third party notice #54103 @mjbvz

Debug

• Provide fine-grained support for smart-step smartStep should only skip unmapped lines in files that have sourcemaps vscode-chrome-debug-core#245 @roblourens @weinand
• Improvements to Node Auto Attach behavior: remember mode Node debug: auto attach mode is not remembered #53586 @weinand
• Don't force-kill debuggees on session end Support DAP's terminate request when ending a debug session #54384 @weinand @isidorn 
• Move 'loaded scripts explorer' into VS Code Move loaded scripts explorer into VS Code #37767 @weinand @isidorn

Extension Contributions

• Support several forthcoming PRs against the xterm.js project such as Initial implementation xtermjs/xterm-addon-ligatures#1 @Tyriar
• 🏃 Provide support for pull requests Short term roadmap vscode-pull-request-github#1 @RMacfarlane @rebornix @shana @daviwil @sguthals
• Improve end-2-end test coverage of the Vetur LS Cover Vetur's Language Features with ene-to-end tests vuejs/vetur#802 @octref

Extensions

• Support for Extension Packs independent of the 'extensionDependencies' property Suggestion: Allow extension packs to not be defined by dependencies #48430 @sandy081
• Improve presentation and detail pages of built-in extensions Improve presentation of the built in extensions view in the details section #54098 @ramya-rao-a
• Provide completion proposals in the search box of the Extensions view Improve discoverability of search filters in the extensions sidebar #46333 @JacksonKearl

API

• Finalize API for
  • SearchProvider, support to invoke find in files programmatically Search Provider extension API #47058 @roblourens
  • Terminal API Stabilize terminal access APIs #52574 @Tyriar
  • Support for custom editor tab icons for webviews Allow webview panels to provide a custom icon #48864 @mjbvz
  • Compute definition locations Finalize DefinitionLink api #54101 @mjbvz
  • Resource level workspace edits WorkspaceEdit should support creating, deleting, and renaming of files #10659 @jrieken
  • Quick input improvements QuickInput API feedback #53327 @chrmarti
  • Protocol handler Public API: Support URL handling #48426 @joaomoreno
• Propose API
  • Custom views, support decorations on items Support proposed DecorationProvider api on custom views #47502 @sandy081

Engineering

• Adopt Electron 2.0 Electron v2.0.0 #48290 @bpasero @Tyriar
• Foundational work to remove TPromise from the code base Electron v2.0.0 #48290 @joaomoreno @jrieken
• 🏃 Provide tooling for extracting telemetry event summary Allow developers to create catalog of all telemetry events based on our GDPR code annotations #54401 @kieferrm
• Show a window layout 'preview' during startup Parts splash #53871 @jrieken

Documentation

• Update intro videos for getting started and debugging Update intro videos for getting started and debugging vscode-docs#1706 @auchenberg

---

Deferred Items

• Trigger characters for signature help Add trigger character to SignatureHelpProvider #51731 @mjbvz (will come up with more complete api proposal for next iteration)
• Support downloading of additional resources when installing an extension Support downloading of additional resources when installing an extension #53855 @sandy081
• Tree widget optimizations for Outline @joaomoreno
• Explore fluent design options Allow for transparent / vibrant window theme #32257 Windows, macOS and Linux transparency #52707 @sbatten @bpasero
• Finish read only workspace support (dynamically enable/disable) Editor buffers readonly status doesn't change after changing file system provider #53256 LiveShare: Improve support for dirty readonly files #53257 @isidorn
• Investigate into automated daily startup performance regression testing @jrieken
• more improvements for Node Auto Attach discoverability Improvements to Node Auto Attach to improve defaults and discoverability #53640 @weinand