Iteration Plan for January 2018

[kieferrm]

Happy 2018 everyone! This plan captures our work in January. This is a 5 week iteration. We will ship early February.

Endgame

• January 29th: Code freeze for the endgame
• February 2nd: Endgame done

The endgame details for this iteration are tracked in #42374

Plan Items

Below is a summary of the top level plan items. Given the large number of explorations, we'll diverge from our usual practice of having plan items for all bullets upfront. This time we'll add them as we go.

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

Install/Update

• Investigate in improving the update experience on Windows Improve Windows update experience #41676 @joaomoreno

Workbench

• Switch to async dialog API Change to use async API for modal dialogs #39536 @bpasero
• Support saving a file in admin mode Allow to save files that need user elevation #1614 @bpasero
• UX for notification improvements UI - explore improved notification UX #22388 @bpasero @stevencl
• Multi-select in the Explorer, Open Editor Implement multi-select in left-panel file tree #1023 @isidorn
• Reimplement drop downs for Linux/Windows (themable, fixes initial empty contents) UI Theme Add: select-box(drop downs) selection and hover colors #25965 (PR @cleidigh) @bpasero
• Enable Error decorations in explorer highlight files in the file explorer that have errors #782 @jrieken
• Support natural language search in Settings editor Implement settings search UX with split "filter" and "natural language" sections #40957 @roblourens
• Explore improving how a user changes a setting Explore improvements to settings editor #41040 @roblourens @sandy081

Editor

• Text model and storage reimplementation to improve performance Explore new text buffer for performance improvement #41042 @alexandrudima @rebornix
• Allow to save large files > 256 MB Not possible to save huge file ("Invalid string length") #32503 @bpasero @alexandrudima
• Support language-type independent snippets [snippets] Global snippet option #13182 @jrieken
• More customization for the caret Support customization of cursor width #41052 @ramya-rao-a

Debug

• Launch configs for multi root workspaces Multi-root: support Compound debug configurations across workspace folders #38134 @isidorn
• Support auto attach for node.js subprocess (aka cluster support) Support auto attach for node.js subprocesses (aka cluster support) #40123 @weinand
• Support to use nvm configuratons in node launch configs consider to support "nvm" in node-debug extension #25386 @weinand
• Explore how to run DebugAdapter inside extension Explore how to run a DebugAdapter inside the extension (instead of separate process) #40906 @weinand

Terminal

• Improve accessibility of built-in terminal Integrated terminal does not support screen readers #8339 @Tyriar

SCM

• Submodule support @joaomoreno
• Git commit message length counter @joaomoreno

Output Panel

• Show product logs in the output panel Logs should be in the output panel #39638 @sandy081
• Make log viewing in output panel more memory efficient Make Output panel memory efficient #40196 @sandy081

Languages

Language Server Support

• Create a website for LSP @dbaeumer @auchenberg
• Protocol extension for goto implementation Add ImplementationProvider Support language-server-protocol#156 @dbaeumer

Emmet

• Explore how to improve emmet activation in html and css files Consider moving emmet completion provider for css to css language service #29113 @ramya-rao-a

JavaScript/TypeScript

• Adoption of TS 2.7 Adopt TS 2.7 #41046 @mjbvz

CSS/HTML

• Catchup with latest CSS/Less syntax Less :matches() is not supported vscode-css-languageservice#56 [SCSS] Syntax Error when !important as arguments of Method vscode-css-languageservice#57 [less] identifier expected when using @media (@var) syntax vscode-css-languageservice#58 Add support for CSS next vscode-css-languageservice#47 @octref @aeschli

Extensions

• vsce - Warn when package.json misses repository entry Warn vsce when package.json misses a repository field #41677 @joaomoreno
• Improve quality of recommended extensions Dynamic workspace recommendations #41054 @ramya-rao-a
• Tastefully extend recommendations to a wider range of file types Add extension recommendations for mimetypes not supported out of the box #38543 @ramya-rao-a

Extension Contributions

• Refresh JS Hint support Refresh JSHint support vscode-jshint#48 @RMacfarlane

API

• Migrate proposed Code action API to stable CodeAction api change proposal  #34664 @jrieken @mjbvz
• Propose API to resolve rename/definition scope Rename provider should support to 'resolve' rename location (to expand, invalidate, etc) #7340 @jrieken @mjbvz
• Explore improving the HTMLPreview support Explore improving HTMLPreview #41047 @mjbvz @jrieken
• Propose refactoring provider API Propose refactoring API #41048 @jrieken @mjbvz
• Expose logging API to extensions Expose log level and log path to extensions #40053 @roblourens
• Propose Search Provider API @jrieken, @roblourens
• Propose API to create/delete/rename resources for refactorings @jrieken @mjbvz
• Enhance custom tree view API, primary actions, use icons from resource URI, preserve expansion state, improve managing contributions Enhance custom tree views  #27823 @sandy081
• Debug API to create/remove breakpoints @weinand
• Support to modify the root folder of a workspace Provide additional workspace API (read / write) #35407 @bpasero

Performance

• 🏃 Use ASAR for bundled node modules Explore using ASAR #41350, Use ASAR #41353 @alexandrudima
• Explore using plain nodejs for helper processes Explore using plain node.js for helper processes #41685 @alexandrudima
• Explore local storage replacement localStorage access is slow #18439 @bpasero

Serviceability

• Issue reporter in separate renderer windows Add issue reporter which launches in separate window #41041 @RMacfarlane @octref
• Logs
  • Propagate log level to all processes dynamically El editor inicia pero no se puede ver nada, aparece todo negro #39754 @sandy081
  • Support to upload logs Log file uploader - client side, master issue #40056 @mjbvz @roblourens

Engineering

• Self-host on @ts-check for our JS code Investigation: selfhost on checkJS for our JS code #41678 @joaomoreno @egamma
• 🏃 Support extensions that contribute translations aka "language packs" Proposal: Language Packs #39178 @dbaeumer @sandy081 @aeschli
• 🏃 Tool to generate/update a language pack from transifex Tool to generate/update a language pack from transifex #41682 @aeschli
• Speed up gulp-build @alexandrudima
• Improve issue tracking support bot @chrmarti
  • Delay action of auto-assignment bot by 15s Make bot assign issues to owners with a 1 minute timeout #33999
  • Explore support for detecting duplicate issues Explore support for detecting duplicate issues #41292

Documentations

• Make 5min Node.js debugging video to be embedded in docs and uploaded to YouTube channel @auchenberg
• Add Debugging Recipe for VueJS. Add recipe for VueJS vscode-recipes#55 @auchenberg

---

Deferred

• Improve documentation of our electron upgrade process Improve documentation of our electron upgrade process #41036 @Tyriar

• Add intelisense support for src attributes and href in html [html] completions for src, link, href... #2037 @octref @aeschli

• Adopt logging service @joaomoreno the adoption by the Adopt logging service across the workbench #41680 team

• 💪 Render white space for selection option Provide editor.renderWhitespace "selection" option #1477 @ramya-rao-a

• Provide API for creating a file based output channel Allow extensions to create file based output channel  #41672 @sandy081

• ✋ Electron update to 2.0 @Tyriar @bpasero

• 💪 Docathon team

• ✋ Support 32-bit apt repositories Apt/yum repository should contain 32-bit packages #20790 @Tyriar

• Better support for webpack TBD

• Support web-site for issue reporting @octref @RMacfarlane

• Improve stability of smoke test, run it as part of the builds Improve stability of smoke test #41679 # @joaomoreno

• 💪 Process explorer as a separate renderer window Process explorer as a separate renderer window #41045 @RMacfarlane

[takkuumi]

hi,are you sure update electron to 2.0? The last electron version is v1.8.2-beta.3.

[roblourens]

We haven't done it yet, this is just the plan for the month. And the ✋ means we're blocked.

[Eskibear]

I find the following entry in Roadmap#for-extension-authors, seems completed.

Support migrating the publisher of an extension to another publisher

Does this means we can transfer alice.toy-extension to bob.toy-extension, leaving everything else unchanged?

  [UPDATE] The answer is yes.
  

[aberonni]

Hi, sorry to bother, I'm wondering whether you think #14909 might possibly make it into the next iteration? I think it is quite the dealbreaker for a lot of people who aren't using VSCode right now because of that issue.

If not, could you give an update on the issue as to why it is not being developed?

Thanks!

[egamma]

@aberonni we create the iteration plan at the beginning of an iteration (pls see). We understand that this feature has many up votes, but there are others with more votes. All I can say for now is that the feature is on our radar.

[aberonni]

@egamma thanks for getting back to me, that makes perfect sense to me.

[alxgrtnstrngl]

@egamma @kieferrm After a quick look at the top 5 tickets it appears they pertain to UI/UX enhancements and it doesn't appear as if any of them made it into this iteration. Most of these pertain to UI/UX enhancements. Do the items in the January 2018 iteration block many of the items below?

#14444 - vscode.extensions Doesn't Update On Installing / Removing / Disabling Extensions without restarting
#5605 - Feature request: symbols tree view
#10121 - Allow for floating windows
#10546 - Tabs for integrated terminal
#14909 - Support a grid layout for editors

I understand the enhancements above involve a lot work and will probably take more than a few iterations to complete. Is there a way the developer team could create a short-term plan on how to address these? Could you put this in the project wiki or a plan document so users could track them? There needs to be a bit more transparency with the community on these sorts of initiatives.

Please keep in mind that the above issues are serious blockers for users coming from other editors who want to migrate their workflows to VSCode but can't because the UI/UX isn't as flexible or efficient resulting in a loss of productivity for them.

[egamma]

@alxgrtnstrngl thanks for your feedback. In addition to the iteration plan we also maintain the roadmap for the next 6 months. We update the roadmap based on user feedback. Several of the items you mention above are already on this roadmap.

Our planning process is documented here https://github.com/Microsoft/vscode/wiki/Development-Process

[ghost]

Guys I saw release notes and I'm impressed. Thank you very much! It's my daily tool which I'm using more than 8 hours per day and I'm every single day happy because of VS Code. Thank you very much! That support, activity, features, bug-fixes, team - it's amazing! 🥇

[onetrev]

I'm concerned that "Catchup with latest CSS/less syntax" was checked off when this item that was in the list is still open.

[octref]

@onetrev Getting full PostCSS/cssnext support is going to take multiple iterations. We've started internal discussion and you'll see more work toward it in future iterations.
With that said, if future CSS features come out of the draft phase, become spec and get supported by major browsers, we will support those features in vscode-css-languageservrice.

[kieferrm]

Shipped. Closing.