1.81 highlights and social image
This commit is contained in:
Greg Van Liew
Родитель
5f84f75ec6
Коммит
c76046431f
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8275f9380c15f45ae51dca7fec40defe31f895c8fb7e98ac8515b2dfea96704b
|
||||
size 38869
|
||||
|
|
@ -11,26 +11,31 @@ DownloadVersion: 1.81.0
|
|||
|
||||
<!-- DOWNLOAD_LINKS_PLACEHOLDER -->
|
||||
|
||||
Welcome to the Insiders build. These are the preliminary notes for the July 1.81 release of Visual Studio Code. As we get closer to the release date, you'll find details below about new features and important fixes.
|
||||
Welcome to the July 2023 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:
|
||||
|
||||
Until the July milestone release notes are available, you can still track our progress:
|
||||
* **[Accessibility improvements](#accessibility)** - Accessible View support for notifications, chat responses, and hovers.
|
||||
* **[VS Code Profiles](#profiles)** - Finer control with partial profiles and "Apply to all profiles" options.
|
||||
* **[New diff editor features](#diff-editor)** - Collapse unchanged regions, better diff region text alignment.
|
||||
* **[Git repositories with symlinks](#support-git-repositories-with-symbolic-links)** - Support for repository paths with symbolic links.
|
||||
* **[Notebook updates](#notebooks)** - Search text in closed notebooks, "sticky scroll" displays Markdown headers.
|
||||
* **[Python test discovery](#python)** - Error tolerant pytest discovery continues across all files.
|
||||
* **[Access Jupyter servers in GitHub Codespaces](#jupyter)** - Connect to a remote Jupyter server running in a codespace.
|
||||
* **[GitHub pull request creation](#github-pull-requests-and-issues)** - Better base branch detection, remember previous create PR options.
|
||||
* **[Preview: GitHub Copilot UX](#github-copilot)** - Quick Chat improvements, iterative /fix command.
|
||||
|
||||
* **[Commit log](https://github.com/Microsoft/vscode/commits/main)** - GitHub commits to the vscode open-source repository.
|
||||
* **[Closed issues](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22July+2023%22+is%3Aclosed)** - Resolved bugs and implemented feature requests in the milestone.
|
||||
>If you'd like to read these release notes online, go to [Updates](https://code.visualstudio.com/updates) on [code.visualstudio.com](https://code.visualstudio.com).
|
||||
|
||||
We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.
|
||||
|
||||
>If you'd like to read release notes for previous VS Code versions, go to [Updates](https://code.visualstudio.com/updates) on [code.visualstudio.com](https://code.visualstudio.com).
|
||||
**Insiders:** Want to try new features as soon as possible? You can download the nightly [Insiders](https://code.visualstudio.com/insiders) build and try the latest updates as soon as they are available.
|
||||
|
||||
## Accessibility
|
||||
|
||||
### Accessible View improvements
|
||||
|
||||
The **Open Accessible View** (`kb(editor.action.accessibleView)`) command allows screen reader users to inspect content character by character, line by line. Last iteration, we added accessible views for editor hovers and chat panel responses.
|
||||
The **Open Accessible View** (`kb(editor.action.accessibleView)`) command allows screen reader users to inspect content character by character, line by line. Last iteration, we added Accessible Views for editor hovers and chat panel responses.
|
||||
|
||||
There are now accessible views for notifications, inline chat responses, Jupyter notebook output, and workbench hovers.
|
||||
There are now Accessible Views for notifications, inline chat responses, Jupyter notebook output, and workbench hovers.
|
||||
|
||||
When an element that offers an accessible view is focused, a hint is provided in the ARIA label. That hint can be disabled per feature via the `accessibility.verbosity` setting.
|
||||
When an element that offers an Accessible View is focused, a hint is provided in the ARIA label. That hint can be disabled per feature via the `accessibility.verbosity` setting.
|
||||
|
||||
There are **Show Next in Accessible View** (`kb(editor.action.accessibleViewNext)`) and **Show Previous in Accessible View** (`kb(editor.action.accessibleViewPrevious)`) commands for easy navigation between elements in the chat panel and notifications list.
|
||||
|
||||
|
|
@ -46,12 +51,6 @@ The experience when navigating between an input control (for example, search or
|
|||
|
||||
In the diff editor, the **Difference Review Pane** was renamed to **Accessible Diff Viewer**. The accessible diff viewer addresses accessibility shortcomings of the diff editor and can be opened with `kb(editor.action.accessibleDiffViewer.next)` or the **Open Accessible Diff Viewer** command from the diff editor **More Actions** menu. Along with this rename, we also fixed some bugs and added some new features, such as being able to launch the Accessibility Help dialog or jump to the modified editor from the viewer.
|
||||
|
||||
## Workbench
|
||||
|
||||
### Release notes for upcoming update
|
||||
|
||||
Whenever a monthly stable update is ready to be installed, you can now preview the release notes via the **Show Update Release Notes** command in the **Manage** menu (gear button) at the bottom of the Activity bar.
|
||||
|
||||
## Profiles
|
||||
|
||||
### Support for partial profiles
|
||||
|
|
@ -94,8 +93,20 @@ This makes this extension available in all profiles. You can revert this by unch
|
|||
|
||||
The `workbench.action.openSettingsJson` command will now open the profile-specific settings JSON file when a user is in a non-default profile. To show application-scoped settings, use the `workbench.action.openApplicationSettingsJson` command instead.
|
||||
|
||||
## Workbench
|
||||
|
||||
### Release notes for upcoming update
|
||||
|
||||
Whenever a monthly stable update is ready to be installed, you can now preview the release notes via the **Show Update Release Notes** command in the **Manage** menu (gear button) at the bottom of the Activity bar.
|
||||
|
||||
## Editor
|
||||
|
||||
### Markdown paste URLs as formatted links
|
||||
|
||||
The `markdown.editor.pasteUrlAsFormattedLink` setting now has a new option of `smart`. The `smart` paste feature can now detect when you are pasting into text where you may not want automatic Markdown link formatting. Some situations that `smart` pasting ignores include pasting within a Markdown link, over another Markdown link, and within a code block.
|
||||
|
||||
By default, the `pasteUrlAsFormattedLink` feature is currently off (`never`), but you can change the setting to `smart` or `always` (always create a formatted URL link).
|
||||
|
||||
### Asynchronous tokenization rollout
|
||||
|
||||
In the [1.76 update](https://code.visualstudio.com/updates/v1_76#_asynchronous-tokenization), we implemented editor document asynchronous tokenization on a web-worker to improve the performance of the renderer process. Since then, we have fixed several bugs caused by rare race conditions and with this release, we are starting to roll out this feature to Stable users.
|
||||
|
|
@ -166,14 +177,12 @@ Based on community feedback, there is now support for Git repositories that have
|
|||
|
||||
## Debug
|
||||
|
||||
### JavaScript Debugger
|
||||
### JavaScript debugger
|
||||
|
||||
#### Support for the Fast Node (Version) Manager
|
||||
|
||||
The JavaScript debugger now supports the [Fast Node Manager](https://github.com/Schniz/fnm) (fnm) in its runtime version. Users of fnm can now use the `runtimeVersion` property of `launch.json` to select the Node.js version to use.
|
||||
|
||||
## Languages
|
||||
|
||||
## Notebooks
|
||||
|
||||
### Rich content search for closed notebooks
|
||||
|
|
@ -206,6 +215,12 @@ This release brings the first iteration of "sticky scroll" for the notebook edit
|
|||
|
||||
The [Remote Development extensions](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack), allow you to use a [Dev Container](https://code.visualstudio.com/docs/devcontainers/containers), remote machine via SSH or [Remote Tunnels](https://code.visualstudio.com/docs/remote/tunnels), or the [Windows Subsystem for Linux](https://learn.microsoft.com/windows/wsl) (WSL) as a full-featured development environment.
|
||||
|
||||
Highlights include:
|
||||
|
||||
* Install Remote Tunnels as a service from VS Code.
|
||||
* Simplified @devcontainers/cli installation.
|
||||
* Record Dev Container Feature dependencies in a lockfile.
|
||||
|
||||
You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_81.md).
|
||||
|
||||
## Contributions to extensions
|
||||
|
|
@ -266,7 +281,7 @@ The following recording illustrates all three improvements:
|
|||
|
||||
#### Terminal context
|
||||
|
||||
Copilot chat ow knows about the active terminal's buffer and selection.
|
||||
Copilot Chat now knows about the active terminal's buffer and selection.
|
||||
|
||||
### Python
|
||||
|
||||
|
|
@ -303,7 +318,7 @@ When working on Jupyter notebook on [github.dev](https://github.dev), you can no
|
|||
|
||||
<video src="images/1_81/connect-to-codespace.mp4" autoplay loop controls muted title="Connect to Jupyter Server on GitHub Codespaces"></video>
|
||||
|
||||
## Continue On with uncommitted changes
|
||||
#### Continue On with uncommitted changes
|
||||
|
||||
You can switch to the underlying codespace by selecting the **Continue On** button in the notebook toolbar, and any uncommitted changes in the workspace are brought to the codespace.
|
||||
|
||||
|
|
@ -330,14 +345,6 @@ Review the [changelog for the 0.70.0](https://github.com/microsoft/vscode-pull-r
|
|||
|
||||
Previously, when you sign out of a GitHub account in VS Code, it would only remove OAuth tokens from the secrets storage. The token is still valid and able to make requests to GitHub's APIs. To improve the security of token management, we now attempt to [delete the token on the backend](https://docs.github.com/en/rest/apps/oauth-applications?apiVersion=2022-11-28#delete-an-app-token) making the token no longer valid after sign out.
|
||||
|
||||
## Preview Features
|
||||
|
||||
### Markdown paste URLs as formatted links
|
||||
|
||||
The `markdown.editor.pasteUrlAsFormattedLink` setting now has a new option of `smart`. The `smart` paste feature can now detect when you are pasting into text where you may not want automatic Markdown link formatting. Some situations that `smart` pasting ignores include pasting within a Markdown link, over another Markdown link, and within a code block.
|
||||
|
||||
By default, the `pasteUrlAsFormattedLink` feature is currently off (`never`), but you can change the setting to `smart` or `always` (always create a formatted URL link).
|
||||
|
||||
## Extension authoring
|
||||
|
||||
### revealSetting and focusSearch added to IOpenSettingsActionOptions
|
||||
|
|
@ -352,7 +359,7 @@ vscode.commands.executeCommand('workbench.action.openSettingsJson', { revealSett
|
|||
|
||||
opens the user settings JSON file, and then reveals the `editor.renderWhitespace` setting if it exists.
|
||||
|
||||
### New `TestController.invalidateTestResults` method
|
||||
### New TestController.invalidateTestResults method
|
||||
|
||||
Test extensions can call the new method `TestController.invalidateTestResults` to indicate to the user that any results for one or more tests may no longer be applicable. For example, an extension might do something like:
|
||||
|
||||
|
|
@ -381,16 +388,6 @@ The API for icons in `QuickPickItem` has been finalized. You can now use the `ic
|
|||
|
||||
|
||||
|
||||
## Proposed APIs
|
||||
|
||||
Every milestone comes with new proposed APIs and extension authors can try them out. As always, we want your feedback. Here are the steps to try out a proposed API:
|
||||
|
||||
1. [Find a proposal that you want to try](https://github.com/microsoft/vscode/tree/main/src/vscode-dts) and add its name to `package.json#enabledApiProposals`.
|
||||
1. Use the latest [@vscode/dts](https://github.com/microsoft/vscode-dts) and run `npx @vscode/dts dev`. It will download the corresponding `d.ts` files into your workspace.
|
||||
1. You can now program against the proposal.
|
||||
|
||||
You cannot publish an extension that uses a proposed API. There may be breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
## Engineering
|
||||
|
||||
### Shrinking VS Code with name mangling
|
||||
|
|
@ -401,20 +398,20 @@ A recent engineering effort reduced the size of VS Code's shipping JavaScript by
|
|||
|
||||
Continuing on from [last month's improvements](https://code.visualstudio.com/updates/v1_80#_terminal-pty-host-improvements) to the pty host, the following improvements have been made:
|
||||
|
||||
- Performance
|
||||
- The pty host now only launches when it's needed, so users that never open the terminal will save around 50-100mb.
|
||||
- Further parallelization of terminal reconnection, speeding up the time to initialize the terminal.
|
||||
- Terminal output messages are now buffered, reducing traffic going from the pty host and the window hosting the terminal.
|
||||
- Diagnostics
|
||||
- Latency stats between each process are logged when in trace log level.
|
||||
- The window ID is logged to all logs in the **Terminal** output channel.
|
||||
- Pty host RPC logging now logs responses that failed as a result of an exception.
|
||||
* Performance
|
||||
* The pty host now only launches when it's needed, so users that never open the terminal will save around 50-100 MB.
|
||||
* Further parallelization of terminal reconnection, speeding up the time to initialize the terminal.
|
||||
* Terminal output messages are now buffered, reducing traffic going from the pty host and the window hosting the terminal.
|
||||
* Diagnostics
|
||||
* Latency stats between each process are logged when in trace log level.
|
||||
* The window ID is logged to all logs in the **Terminal** output channel.
|
||||
* Pty host RPC logging now logs responses that failed as a result of an exception.
|
||||
|
||||
## Notable fixes
|
||||
|
||||
* Reattached to the wrong terminal [#133542](https://github.com/microsoft/vscode/issues/133542)
|
||||
* Better object completions in the JavaScript debugger [#168021](https://github.com/microsoft/vscode/issues/168021)
|
||||
* Cannot click and drag scroll bar in terminal [#184894](https://github.com/microsoft/vscode/issues/184894)
|
||||
* [133542](https://github.com/microsoft/vscode/issues/133542) Reattached to the wrong terminal
|
||||
* [168021](https://github.com/microsoft/vscode/issues/168021) Better object completions in the JavaScript debugger
|
||||
* [184894](https://github.com/microsoft/vscode/issues/184894) Cannot click and drag scroll bar in terminal
|
||||
|
||||
## Thank you
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,5 @@
|
|||
# July 2023 (version 1.81)
|
||||
|
||||
## Core
|
||||
|
||||
## Tunnels
|
||||
|
||||
### Install Tunnels as a service from VS Code
|
||||
|
|
@ -10,8 +8,6 @@ Using the **Remote Tunnels: Turn on Remote Tunnel Access** command, users now ha
|
|||
|
||||
When installed as a service, the **Turn off Remote Tunnel Access** command will uninstall the service.
|
||||
|
||||
## SSH
|
||||
|
||||
## Dev Containers
|
||||
|
||||
### Simplified @devcontainers/cli installation
|
||||
|
|
@ -23,5 +19,3 @@ You no longer need a build toolchain to install the [@devcontainers/cli](https:/
|
|||
[Feature](https://code.visualstudio.com/docs/devcontainers/containers#_dev-container-features) dependencies are now also recorded in the `devcontainer-lock.json`. You can enable the use of lockfiles with the `dev.containers.experimentalLockfile` user setting:
|
||||
|
||||
|
||||
|
||||
## WSL
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче