Iteration Plan for August 2018

[kieferrm]

This plan captures our work in August. This is a 4-week iteration. We will ship our August Update in early September. August is the second of our two Summer iterations. Those of us who didn't take time off earlier are doing so now.

Nevertheless, work will be done. We'll move the new settings experience out of preview and we'll publish a preview of the GitHub pull request extension. We'll also continue improving the accessibility of VS Code (keyboard navigation and screen reader support).

Endgame

• August 27th, 2018: Code freeze for the endgame
• August 31st, 2018: Endgame done

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

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 Settings editor backlog #55791 @roblourens
• Support @ queries in the new settings experience Intellisense in settings editor search bar for available filters #55804 @JacksonKearl
• In Settings search, provide a way to show matching but not-installed extensions Show settings search matches from non-installed extensions #49474 @roblourens
• Support OS-specific keybindings OS Specific Keybindings #8962 @Tyriar
• Polish custom titlebar and menus (see titlebar and menus query) @sbatten
• 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
• Revisit layout of global menu bar @bpasero
• Polishing breadcrumbs interactions @jrieken
• Adapt search viewlet/panel to support preview options of proposed search provider API Implement previewOptions for TextSearchProvider extension API #57186 @roblourens

Monaco Editor

• Ship a new version of the Monaco editor @alexandrudima

Terminal

• 🏃 Explore support for the Windows ConPTY API Windows terminal issues caused by winpty #45693 @Tyriar

Languages

CSS

• File Path completion for css/sass @import and url() SCSS file path autocomplete not working after 1.24.0 release #51331 @octref
• Go to definition for css/sass @import and url() [css/scss] Go to definition for css/sass @import #29899 @octref

Language Server Protocol

• Propose support for workspace resource edits @dbaeumer
• Publish json tracing format for LSP and add support in vscode-languageserver-node. Extend Node SDK to allow JSON format output language-server-protocol-inspector#8 @octref
• Allow live-streaming LSP communication into the LSP Inspector Allow streaming LSP communication into the inspector language-server-protocol-inspector#5 @octref

Debug

• Remove workaround added for "Reload window" breaks EH debugging #55955 @isidorn
• 🏃 Explore API for injecting a middleman into DAP communication Explore API for injecting a middle-man into DAP communication #55945 @weinand
• Help making EH debugging work in Live Share Figure out why EH debugging doesn't work in Live Share #56471 @weinand
• Improvements to Node Auto Attach: don't auto attach to regular launches do not attach to node.js processes that are already being debugged #57232 @weinand
• Move 'loaded scripts explorer' into VS Code Move loaded scripts explorer into VS Code #37767 @weinand

Extension Contributions

• Support PRs against xterm.js 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
• Explore and plan to migrate vscode-tslint toward using tslint as a TypeScript server plugin @mjbvz @egamma
• Update Vetur roadmap. Vetur 1.0 Roadmap vuejs/vetur#873 @octref

Extensions

• Include Extensions in the Preferences menu and Recommended extensions in default view when no installed extensions Include Extensions in the Preferences menu #56042 @ramya-rao-a
• Ensure extension authors use well-formed URIs where needed (follow-up of Issue Opening Folder Using vscode.openFolder #55891) Inform extensions that call 'vscode.openFolder' with file URIs created with URI.parse #57267 @aeschli

API

• Clarify how to use vscode.URI Add more documentation to vscode-uri to illustrate usage #56108 @jrieken
• Finalize API for
  • 🏃 💪 Search Provider API Search Provider extension API #47058 (comment) @roblourens
  • Logging API Promote extension log API to stable #43276 (comment) @jrieken
• Propose API
  • 🏃 Disable auto-ident on completion item for space sensitive languages Allow CompletionItem to control how text is being inserted #57093 @jrieken
  • Expose selected source control providers @joaomoreno
  • 🔴 🏃 Allow extensions to use the built-in git extension @joaomoreno

Engineering

• Progress on TPromise removal (remove use of cancelation and progress support) WinJS.Promise removal plan #53526 @jrieken
• 🔴 🏃 Investigate automated startup performance regression testing @jrieken
• Explore using webpack to bundle the git extension @jrieken
• Measure performance impact when search runs as an extension Add performance telemetry for search in EH vs own proc #56950 @roblourens

Documentation

• 🏃 Update videos for Customization and Code editing Update intro videos for Customization and Code editing vscode-docs#1751 @auchenberg

---

Deferred Items

• Support case-sensitive FileSystemProviders Case-sensitivity and file system providers #48258 @isidorn
• Update interface overview @chrmarti
• Trigger characters for signature help Add trigger character to SignatureHelpProvider #51731 @mjbvz
• Explore support for extensions to download additional resources Support downloading of additional resources when installing an extension #53855 @sandy081 @joaomoreno
• Tree widget optimizations for Outline @joaomoreno
• ✋ Update vscode-extension-telemetry module to finialized Logging API Extension telemetry is not logged into log files when log level is changed to trace #55398 @ramya-rao-a
• Provide tooling for extracting telemetry event summary Allow developers to create catalog of all telemetry events based on our GDPR code annotations #54401 @kieferrm

[ghost]

Typo

[shanalikhan]

Guys,
This issue #14444 needs your love.
This single thread have over 900 votes.

[myfairsyer]

There's an issue for the August endgame now: #57245

[egamma]

@myfairsyer thanks, updated the description with link to the endgame issue.

[myfairsyer]

@myfairsyer thanks, updated the description with link to the endgame issue.

Thanks. I also filed a PR for the Interation Plans Wiki page