Welcome to the July 2020 release of Visual Studio Code. There are a number of updates in this version that we hope you will like, some of the key highlights include:
If you’d like to read these release notes online, go to Updates on code.visualstudio.com.
Join us live at the VS Code team’s livestream on Monday, August 17 at 9am Pacific (5pm London), to see a demo of what’s new in this release and ask us questions live.
Insiders: Want to try 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!
This milestone, we again received helpful feedback from our community, which helped us identify and tackle accessibility issues.
We added an Open Search Editor command to open an existing search editor if one exists, or to otherwise create a new one. The pre-existing command Open new Search Editor has been renamed to New Search Editor, and will always create a new Search Editor.
Search Editors also now support custom search.sortOrder
configurations, such as sorting by file type, modified date, or result count.
The Extensions view filter actions are now displayed under a separate filter action (funnel button):
Theme: GitHub Light
The Extensions view Views and More Actions (…) menu has been refactored for better organization of extension queries (such as Installed or Recommended) and other actions like Check for Extension Updates and Enable All Extensions:
Theme: GitHub Light
There’s a new setting, scm.alwaysShowRepositories
, that makes the Source Control view always show the repository rows, even if there’s only a single repository open:
As you navigate the Source Control view, pressing Space on a change will now open it as a preview editor and keep the focus in the Source Control view, for easier keyboard navigation.
Thanks to the new submenu proposed API, the Git View and More Actions (…) menu has been refactored for better organization of several commands:
When publishing a repository to GitHub, you now have the option to make the repository public, as opposed to the previous default, private:
debug.openDebug
setting has been changed to openOnFirstSessionStart
. As a result, the Debug view will only be automatically opened when the first debug session is started.A new Debug: Open Link command has been added to quickly debug any URL. Previously, to debug a browser, you had to install the Debugger for Chrome extension and write a launch.json
config file to debug a page. This command allows you to debug any URL without needing additional launch configurations.
Theme: Earthsong
If you have a URL selected in your active editor, it will open that automatically. Otherwise, VS Code will prompt you to enter a URL, pre-filling with the URL in your clipboard, if any.
You can adjust the debug configuration used in this command via the debug.javascript.debugByLinkOptions
setting.
The previous release of VS Code included our new JavaScript debugger. We’d like to thank the community for your feedback on it, and this release includes dozens of resulting fixes and improvements. If you run into any issues with debugging, please make sure to file an issue if you haven’t already.
All of the text file encodings of the desktop version of VS Code are now also supported when running in a browser.
#visual studio code #visual studio #code