Updates from release notes reading
This commit is contained in:
gregvanl
Родитель
3f6c1896f3
Коммит
99b6e56744
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ec60dad0bf3265bb7a9509f0f83bbfa8fcbc30dced98b910af938b8a0a43f590
|
||||
size 40209
|
||||
oid sha256:66a3db2779edd09177b8721f7d04059f54fd734d5e11211b444bd30c697afaa7
|
||||
size 37923
|
||||
|
|
|
|||
|
|
@ -39,9 +39,9 @@ To accept a notification's primary action, users have historically needed to nav
|
|||
|
||||
It is now possible to focus on the hover widget and scroll horizontally and vertically with the `up`, `down`, `home`, `end`, `page up` and `page down` keys. The keybindings to focus the hover are by default the same as the keybindings to show the hover at the primary cursor position.
|
||||
|
||||
### Sticky scroll navigation
|
||||
### Sticky Scroll navigation
|
||||
|
||||
It is now possible to focus on the sticky scroll lines and navigate with the `up` and `down` keys. You may use the `enter` key to reveal a selected line. To focus on the sticky scroll, select `Focus Sticky Scroll` from the command palette.
|
||||
It is now possible to focus on the Sticky Scroll lines and navigate with the `up` and `down` keys. You may use the `Enter` key to reveal a selected line. To focus on the Sticky Scroll, you can run **Focus Sticky Scroll** from the Command Palette.
|
||||
|
||||
## Workbench
|
||||
|
||||
|
|
@ -61,11 +61,9 @@ These actions have also been added to the **Share** submenu in the editor tab co
|
|||
|
||||
VS Code can now recommend extensions based on the file content. For example, if you open a Python file that has notebook cells syntax, VS Code recommends the [Jupyter](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) extension that can render and run these cells appropriately.
|
||||
|
||||
## Editor
|
||||
### Select default provider for Sticky Scroll
|
||||
|
||||
### Select default provider for sticky scroll
|
||||
|
||||
It is now possible to choose between the outline provider model, the folding provider model and the indentation model to determine which lines to stick in sticky scroll. Each model, if non-existent, falls back onto the next model in the aforementioned order. This setting can be changed under `Editor > Sticky Scroll: Default Model`.
|
||||
It is now possible to choose between the outline provider model, the folding provider model, and the indentation model to determine which lines to stick in the Sticky Scroll UI. Each model, if not available for the current language, falls back onto the next model in the aforementioned order. This setting can be changed under **Editor > Sticky Scroll: Default Model** (`editor.stickyScroll.defaultModel`).
|
||||
|
||||
## Terminal
|
||||
|
||||
|
|
@ -151,13 +149,19 @@ The [Remote Development extensions](https://marketplace.visualstudio.com/items?i
|
|||
|
||||
A Dev Container lets you use a container as a full-featured development environment. The [Dev Container Specification](https://containers.dev/) seeks to find ways to enrich existing formats with common development specific settings, tools, and configuration while still providing a simplified, un-orchestrated single container option. You can learn more about Dev Containers and their spec in a [new episode of the Changelog podcast](https://changelog.com/podcast/529).
|
||||
|
||||
Other highlights include:
|
||||
|
||||
* Remote Tunnels - Better reuse of existing tunnels.
|
||||
* Remote Tunnels - **Continue Working in VS Code Desktop** command to quickly transition to local development.
|
||||
* Dev Containers - Easier clean up of unused Dev Containers and volumes.
|
||||
|
||||
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_77.md).
|
||||
|
||||
## Extensions
|
||||
|
||||
### Not blocking installing extensions when extension signature verification fails
|
||||
|
||||
Extension signature verification is reporting errors for a small number of valid extensions and causing them to not be installed. This is caused by bugs in the VS Marketplace and VS Code and we are actively working on fixing them. In order to unblock the install flow, VS Code will continue to install extensions even if signing verification fails. We will make signature verification blocking again once [this bug](https://github.com/microsoft/vsmarketplace/issues/619) is fixed, most likely in our next Stable release.
|
||||
Extension signature verification is reporting errors for a small number of valid extensions and causing them to not be installed. This is caused by bugs in the VS Marketplace and VS Code and we are actively working on fixing them. In order to unblock the install flow, VS Code will continue to install extensions even if signing verification fails. We will make signature verification blocking again once [VS Marketplace issue #619](https://github.com/microsoft/vsmarketplace/issues/619) is fixed, most likely in our next Stable release.
|
||||
|
||||
## Contributions to extensions
|
||||
|
||||
|
|
@ -187,13 +191,13 @@ Example usages can be found in the [Python Environment APIs](https://github.com/
|
|||
|
||||
### Jupyter
|
||||
|
||||
### Kernel picker improvements for Python Environments
|
||||
### Kernel picker improvements for Python environments
|
||||
|
||||
The kernel picker now lists `Conda Environments` without Python installed in them.
|
||||
The kernel picker now lists **conda environments** without Python installed in them.
|
||||
|
||||
For instance if a new `Conda Environment` is created using a CLI such as `conda creeate -n envML`, this new environment will be displayed in the list of [Python Environments](https://code.visualstudio.com/docs/datascience/jupyter-kernel-management#_python-environments) under a section `Conda Env Without Python`.
|
||||
For example, if a new conda environment is created using a CLI such as `conda create -n envML`, this new environment is displayed in the list of [Python Environments](https://code.visualstudio.com/docs/datascience/jupyter-kernel-management#_python-environments) under a section **Conda Env Without Python**.
|
||||
|
||||
Upon selecting such an environment, the Python runtime and necessary dependencies will be automatically installed into the selected environment.
|
||||
Upon selecting such an environment, the Python runtime and necessary dependencies are automatically installed into the selected environment.
|
||||
|
||||
|
||||
|
||||
|
|
@ -202,7 +206,7 @@ Upon selecting such an environment, the Python runtime and necessary dependencie
|
|||
There has been more progress on the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, which allows you to work on, create, and manage pull requests and issues. Highlights include:
|
||||
|
||||
* Pull requests can be opened on vscode.dev from the Pull Requests view.
|
||||
* There's a new setting to check the "auto-merge" checkbox in the Create view: `githubPullRequests.setAutoMerge`.
|
||||
* There's a new setting to check the **Auto-merge** checkbox in the Create view: `githubPullRequests.setAutoMerge`.
|
||||
|
||||
Check out the [changelog for the 0.62.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0620) release of the extension to see the other highlights.
|
||||
|
||||
|
|
@ -216,9 +220,9 @@ Last iteration, we introduced global search for formatted notebook content in op
|
|||
Sorry, your browser doesn't support HTML 5 video.
|
||||
</video>
|
||||
|
||||
### Remote Connection Picker in the Welcome Page start list
|
||||
The Welcome page now supports an experimental remote connection picker in the start list to help you get started with remote connections by surfacing remote actions right from the welcome page.
|
||||
This feature is disabled by default and can be enabled by `setting workbench.remote.experimental.showStartListEntry` to true.
|
||||
### Remote connection picker on the Welcome page
|
||||
|
||||
The Welcome page now supports an experimental remote connection picker **Connect to..** in the start list to help you get started with remote connections (SSH, Remote Tunnels, GitHub Codespaces, etc.). This feature is disabled by default and can be enabled by `setting workbench.remote.experimental.showStartListEntry` to true.
|
||||
|
||||
## Extension authoring
|
||||
|
||||
|
|
@ -228,7 +232,7 @@ We plan to update to [Electron 22](https://www.electronjs.org/blog/electron-22-0
|
|||
|
||||
We plan to provide a custom memory allocator so that native modules that are not updated will still continue to work, but nevertheless, it is recommended to review your usages of allocated external memory: Please follow the advice in the [Electron Blog post](https://www.electronjs.org/blog/v8-memory-cage#i-want-to-refactor-a-node-native-module-to-support-electron-21-how-do-i-do-that) for how to adopt this change.
|
||||
|
||||
### Finalized Support for Continuous Test Runs
|
||||
### Finalized support for continuous test runs
|
||||
|
||||
Support for [continuous test runs](https://github.com/microsoft/vscode/issues/134941) has been finalized. This API allows users to indicate to test extensions that they want to "watch" tests and continue to run them as changes are made.
|
||||
|
||||
|
|
@ -237,7 +241,7 @@ const profile = ctrl.createRunProfile(/* ... */);
|
|||
+profile.supportsContinuousRun = true;
|
||||
|
||||
function runHandler(request: vscode.TestRunRequest, cancellation: vscode.CancellationToken) {
|
||||
+ if (request.continous) {
|
||||
+ if (request.continuous) {
|
||||
+ startWatchingAndRunningTests(request);
|
||||
+ }
|
||||
|
||||
|
|
@ -245,17 +249,17 @@ function runHandler(request: vscode.TestRunRequest, cancellation: vscode.Cancell
|
|||
}
|
||||
```
|
||||
|
||||
### New when-clause parser
|
||||
### New when clause parser
|
||||
|
||||
This VS Code release includes a new parser for [when clauses](https://code.visualstudio.com/api/references/when-clause-contexts) offering new features (for example, support for parentheses) and better correctness but also stricter rules. The release also includes a linter for when clauses in extension manifest files to make sure they are syntactically correct. We encourage you to check your when clauses for possible breakage with the new parser. Also, if you use parentheses in when claues, your extension will be compatible with VS Code version 1.77 and later. More information about the changes in this [issue](https://github.com/microsoft/vscode/issues/175540).
|
||||
This VS Code release includes a new parser for [when clauses](https://code.visualstudio.com/api/references/when-clause-contexts) offering new features (for example, support for parentheses) and better correctness but also stricter rules. The release also includes a linter for when clauses in extension manifest files (`package.json`) to make sure they are syntactically correct. We encourage you to check your when clauses for possible breakage with the new parser. Also, if you use parentheses in a when clause, your extension is compatible with VS Code version 1.77 and later. More information about the changes in [issue #175540](https://github.com/microsoft/vscode/issues/175540).
|
||||
|
||||
### Inline completions in SCM input
|
||||
### Inline completions in Source Control input
|
||||
|
||||
The source control input box now supports [inline completions](https://github.com/microsoft/vscode-extension-samples/tree/main/inline-completions):
|
||||
The Source Control input box now supports [inline completions](https://github.com/microsoft/vscode-extension-samples/tree/main/inline-completions):
|
||||
|
||||
|
||||
|
||||
|
||||
The source control input box's document [language id](/docs/languages/identifiers.md) is `scminput`.
|
||||
The Source Control input box's document [language ID](/docs/languages/identifiers.md) is `scminput`.
|
||||
|
||||
## Proposed APIs
|
||||
|
||||
|
|
@ -296,15 +300,15 @@ vscode.workspace.onWillSaveNotebookDocument(e => {
|
|||
|
||||
### EOL warning for windows 8 and 8.1
|
||||
|
||||
VS Code desktop will be updating to Electron >=23 in the next couple of milestones. With the Electron 23 update, VS Code desktop will no longer run on Windows 8 / Windows Server 2012 and Windows 8.1 / Windows Server 2012 R2. In this milestone, we have added deprecation notices for the users on these affected platforms to prepare them for migration. If you are a user of these aforementioned OS versions, please take a look at our [FAQ](https://aka.ms/vscode-faq-old-windows) for additional information.
|
||||
VS Code desktop will be updating to Electron >=23 in the next couple of milestones. With the Electron 23 update, VS Code desktop will no longer run on Windows 8 / Windows Server 2012 and Windows 8.1 / Windows Server 2012 R2. In this milestone, we have added deprecation notices for the users on these affected platforms to prepare them for migration. If you are a user of these aforementioned OS versions, take a look at our [FAQ](https://aka.ms/vscode-faq-old-windows) for additional information.
|
||||
|
||||
### Base image updated for snap package
|
||||
### Base image updated for Snap package
|
||||
|
||||
In this iteration, we have updated our snap package to use Core20 (built from Ubuntu 20.04) as base image from our previous Core (built from Ubuntu 16.04) which addresses missing GLIBC symbols for our CLI, fixes wayland support among others. You can find more context in this [pull request](https://github.com/microsoft/vscode/pull/127320).
|
||||
In this iteration, we have updated our Snap package to use Core20 (built from Ubuntu 20.04) as the base image from our previous Core (built from Ubuntu 16.04). This change addresses missing GLIBC symbols for our CLI and fixes wayland support among other issues. You can find more context in [pull request #127320](https://github.com/microsoft/vscode/pull/127320).
|
||||
|
||||
### Exploring custom memory allocator for the extension host
|
||||
|
||||
To adopt Electron 22 which comes with V8 sandbox enabled and minimize the impact from extensions that rely on native modules which specifically use external array buffers, we have customized the existing memory allocator in the extension host to accommodate the allocations from these native modules to be inside the V8 sandbox as a workaround to avoid FATAL crashes. If you are interested in how/why we ended up with this solution, please check this [issue](https://github.com/microsoft/vscode/issues/177338) for details.
|
||||
To adopt Electron 22, which comes with V8 sandbox enabled, and minimize the impact for extensions that rely on native modules that specifically use external array buffers, we have customized the existing memory allocator in the extension host. Specifically, the extension host now accommodates allocations from these native modules to be inside the V8 sandbox as a workaround to avoid fatal crashes. If you are interested in how/why we ended up with this solution, you can review [issue #177338](https://github.com/microsoft/vscode/issues/177338) for details.
|
||||
|
||||
## Documentation
|
||||
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ When connected to a tunnel in vscode.dev, you can continue in VS Code Desktop wi
|
|||
|
||||
|
||||
|
||||
### Singleton Tunnel Instances
|
||||
### Singleton tunnel instances
|
||||
|
||||
Multiple instances of tunnels running on a machine will be deduplicated. Additional requests to "Turn on Tunnel Access" in the VS Code UI, or running `code tunnel` on the command line, will monitor any existing running tunnel. These monitoring processes still allow you to stop or restart the tunnel by entering "x" or "r" respectively.
|
||||
Multiple instances of tunnels running on a machine will be deduplicated. Additional requests to **Turn on Tunnel Access** in the VS Code UI, or running `code tunnel` on the command line, monitor any existing running tunnel. These monitoring processes still allow you to stop or restart the tunnel by entering "x" or "r" respectively.
|
||||
|
||||
|
||||
|
||||
|
|
@ -30,18 +30,18 @@ A Dev Container lets you use a container as a full-featured development environm
|
|||
|
||||
You can learn more about dev containers and their spec in a [new episode of the Changelog podcast](https://changelog.com/podcast/529).
|
||||
|
||||
### Clean Up Dev Containers and Volumes
|
||||
### Clean up Dev Containers and volumes
|
||||
|
||||
The **Dev Containers: Clean Up Dev Containers...** and **Dev Containers: Clean Up Dev Volumes...** commands let you pick which of the stopped containers and dangling volumes to remove.
|
||||
|
||||
|
||||
|
||||
### Remove Legacy Maven, Gradle and JupyterLab features
|
||||
### Remove legacy Maven, Gradle and JupyterLab features
|
||||
|
||||
We keep working towards replacing the built-in legacy features with their updated counterparts in the contributable container features. The legacy `maven`, `gradle` and `jupyterlab` features are now mapped to the corresponding options on the `ghcr.io/devcontainers/features/java` and `ghcr.io/devcontainers/features/python` features.
|
||||
|
||||
For more information on contributable container features, see the [Dev Container Features](https://containers.dev/implementors/features) documentation.
|
||||
For more information on contributing container features, see the [Dev Container Features](https://containers.dev/implementors/features) documentation.
|
||||
|
||||
### Remove Dependance on Built-In Repository Configurations
|
||||
### Remove dependence on built-in repository configurations
|
||||
|
||||
We have dropped the support for the few built-in Dev Container configurations that were sourced from the [vscode-dev-containers](https://github.com/microsoft/vscode-dev-containers/tree/main/repository-containers/github.com) repository and remain available there.
|
||||
We have dropped support for the few built-in Dev Container configurations that were sourced from the [vscode-dev-containers](https://github.com/microsoft/vscode-dev-containers/tree/main/repository-containers/github.com) repository and remain available there.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче