February 2019 (version 1.32)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. February 2019 (version 1.32) Updates: Issues addressed in each update - 1.32.3 - 1.32.2 - 1.32.1 Downloads for 1.32.3 Windows x64 macOS Intel Linux 64-bit .deb .rpm .tar.gz Linux 32-bit .deb .rpm .tar.gz Welcome to the February 2019 release of Visual Studio Code. There are a number of significant updates in this version that we hope you will like, some of the key highlights include: Preview and apply color themes - Install and apply new theme extensions without reloading.
Keyboard shortcuts editor improvements - Modify keybinding 'when' conditions in the editor. Problems panel hover commands - Apply Quick Fixes or open a Peek window directly from hovers. Preferred Code Actions - Preferred (mostly likely) Code Actions support auto fixing common issues. Debug Console customization - Modify font size, font family, and line height of the Debug Console. Better IntelliSense for ARIA attributes - More detailed descriptions for HTML accessibility attributes.
Vue.js interpolations IntelliSense - The Vetur extension now supports smart completions in Vue.js interpolations. New "Bundling Extensions" topic - Use webpack to improve your extension's load time. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . You can also check out this 1.32 release highlights video from Cloud Developer Advocate Brian Clark . The release notes are arranged in the following sections related to VS Code focus areas.
Here are some further updates: Workbench - Keyboard navigation control, Outline view and breadcrumbs use tree widget. Editor - Fix All Source Action allows you to fix on save, improved column selection. Languages - No reload required when installing TypeScript and Markdown extensions. Extension Authoring - Add commands to the Debug toolbar, track last method signature choice. Insiders: Want to see new features as soon as possible?
You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code ! Workbench Preview and apply new themes You can now preview and apply color and file icon themes immediately after installing an extension that contributes them. Keyboard Shortcuts editor You can now edit the when clause of a keybinding in the Keyboard Shortcuts editor.
We removed the link that opens your keybindings.json file from the Keyboard Shortcuts editor in favor of the {} button on the right of the editor title bar. When directly editing your keybindings.json file, the default keybindings are no longer shown on the left. If you prefer to see Default Keybindings , you can check the Workbench > Settings: Open Default Keybindings setting ( workbench.settings.openDefaultKeybindings to true ).
Automatic Keyboard Navigation setting A new setting List: Automatic Keyboard Navigation controls whether lists and trees capture lexicographic keypresses in order to navigate and filter elements. If disabled, keyboard navigation becomes modal and the list.toggleKeyboardNavigation command will toggle its state. You can assign a specific keyboard shortcut to that command. For example, you could set it to be / and only after pressing / , will subsequent keypresses filter items in lists/trees.
This setting defaults to enabled. Below is the keybinding to toggle keyboard navigation with / for the File Explorer: { "key" : "/" , "command" : "list.toggleKeyboardNavigation" , "when" : "filesExplorerFocus" } Default title bar style on Linux After listening to user feedback, we have made the decision to revert our change of the default setting window.titleBarStyle from custom back to native on Linux. We still recommend the custom title bar for those needing better accessibility support.
More information on this change has been documented in our Linux setup page. New tree widget for Outline and Breadcrumbs The Outline document symbol view and breadcrumb picker have adopted the new tree widget. The new implementation makes them faster and gives better filtering support, along with other new tree widget enhancements. Editor Hover and Problems peek improvements In this release, a command bar with Quick Fix and Peek Problem actions was added to the Problems hover.
The Quick Fix action applies Quick Fixes from the hover and the Peek Problem action will open the peek view in the editor. From a Problems peek view, you can now navigate to the previous and next error/warning. We also improved the appearance of the hovers and the Problems peek view. Hovers with problems and code blocks are given enough space to show their contents: Auto fix and preferred Code Actions The Code Action API powers VS Code's Quick Fixes (the lightbulbs you see in the editor).
Although there may be many Quick Fixes for a given error, there is often one that is the most reasonable fix for the problem. For example, fixing a spelling error is usually the more likely fix than generating new fields. Extensions can now mark a Code Action as "preferred" to indicate that it is the most reasonable fix for the underlying problem. When a preferred fix is available, a blue badge is added to the lightbulb.
Preferred fixes can be automatically applied using the Auto Fix command ( ⌥⌘. (Windows, Linux Shift+Alt+. ) ). Preferred Quick Fixes should generally: Correctly fix the underlying error (and not suppress it). Be a reasonable fix for the error. Not perform extensive operations unexpectedly. Refactoring Code Actions can also be marked as preferred to indicate that they are the most reasonable refactoring. For example, while multiple Extract constant refactorings may be available, the user usually wants to extract to the nearest local.
If that refactoring Code Action is marked isPreferred , users can set up a single keybinding for it: { "key" : "ctrl+shift+r ctrl+e" , "command" : "editor.action.codeAction" , "args" : { "kind" : "refactor.extract.constant" , "preferred" : true } } Fix All Source Actions The new source.fixAll CodeActionKind establishes a convention for extensions that can auto fix errors in a file. This new Source Action kind is similar to Organize imports and makes it easy to configure keybindings for fix all actions or enable auto fix on save: // On save, run both fixAll and organizeImports source actions "editor.codeActionsOnSave" : { "source.fixAll" : true , "source.organizeImports" : true , } The TSLint extension already uses source.fixAll Code Action kind to implement fix all and auto fix on save.
Default keybinding change for expandLineSelection The command expandLineSelection is now bound by default to Ctrl+L ( Cmd+L on macOS) and not to Ctrl+I ( Cmd+I ). Improved column selection With the Multi Cursor Modifier setting configured to use Ctrl ( Cmd on macOS) "editor.multiCursorModifier": "ctrlCmd" , and thus the Alt modifier is only used for Go to Definition, it is now possible to press the Alt modifier when dragging a selection in the editor to toggle between a regular selection or a column selection.
In the following video, the selection begins as a regular selection and then Alt is pressed and held until the mouse button is released: Languages TypeScript 3.3.3 This release includes TypeScript 3.3.3, a small update that fixes a few important bugs . No reload required when installing TypeScript extensions Last iteration , VS Code was changed to no longer require a reload after installing the vast majority of extensions.
VS Code now also supports dynamic loading of TypeScript plugin extensions as well. When you install a new TypeScript extension, such as TSLint , the extension is automatically enabled without requiring a reload. No reload required when installing Markdown extensions In addition, you no longer need to reload VS Code after installing an extension such as GitHub Markdown Preview . Any active Markdown previews will be automatic
The rest of this page is on the live site.