Update vscode repo URLs to default main
This commit is contained in:
gregvanl
Родитель
53dc3646be
Коммит
8007b72c17
|
|
@ -19,7 +19,7 @@ These are the steps for testing Proposed API in local extension development:
|
|||
|
||||
- Use [Insiders](/insiders) release of VS Code.
|
||||
- Add `"enableProposedApi": true` to your `package.json`.
|
||||
- Copy the latest version of the [vscode.proposed.d.ts](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your project's source location.
|
||||
- Copy the latest version of the [vscode.proposed.d.ts](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your project's source location.
|
||||
|
||||
The [vscode-dts](https://github.com/microsoft/vscode-dts) CLI utility allows you to quickly download latest `vscode.proposed.d.ts` for extension development.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,8 +23,8 @@ VS Code provides various APIs that allow you to add your own components to the W
|
|||
|
||||
|
||||
- Activity Bar: The [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice) adds a [View Container](#view-container)
|
||||
- Side Bar: The built-in [NPM extension](https://github.com/microsoft/vscode/tree/master/extensions/npm) adds a [Tree View](#tree-view) to the Explorer View
|
||||
- Editor Group: The built-in [Markdown extension](https://github.com/microsoft/vscode/tree/master/extensions/markdown-language-features) adds a [Webview](#webview) next to other editors in the Editor Group
|
||||
- Side Bar: The built-in [NPM extension](https://github.com/microsoft/vscode/tree/main/extensions/npm) adds a [Tree View](#tree-view) to the Explorer View
|
||||
- Editor Group: The built-in [Markdown extension](https://github.com/microsoft/vscode/tree/main/extensions/markdown-language-features) adds a [Webview](#webview) next to other editors in the Editor Group
|
||||
- Status Bar: The [VSCodeVim extension](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim) adds a [Status Bar Item](#status-bar-item) in the Status Bar
|
||||
|
||||
## Views Container
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Visual Studio Code displays icons next to filenames throughout its UI, and exten
|
|||
|
||||
## Adding a new File Icon Theme
|
||||
|
||||
You can create your own file icon theme from icons (preferably SVG) and from icon fonts. As example, check out the two built-in themes: [Minimal](https://github.com/microsoft/vscode/tree/master/extensions/theme-defaults) and [Seti](https://github.com/microsoft/vscode/tree/master/extensions/theme-seti).
|
||||
You can create your own file icon theme from icons (preferably SVG) and from icon fonts. As example, check out the two built-in themes: [Minimal](https://github.com/microsoft/vscode/tree/main/extensions/theme-defaults) and [Seti](https://github.com/microsoft/vscode/tree/main/extensions/theme-seti).
|
||||
|
||||
To begin, create a VS Code extension and add the `iconTheme` contribution point.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ The Source Control API allows extension authors to define Source Control Managem
|
|||
|
||||
|
||||
|
||||
VS Code itself ships with one Source Control provider, the Git extension, which is the best reference for this API and is [a great starting point](https://github.com/microsoft/vscode/blob/master/extensions/git/src/repository.ts) if you'd like to contribute your very own SCM provider. There are other great examples in the Marketplace such as the [SVN extension](https://marketplace.visualstudio.com/items?itemName=johnstoncode.svn-scm).
|
||||
VS Code itself ships with one Source Control provider, the Git extension, which is the best reference for this API and is [a great starting point](https://github.com/microsoft/vscode/blob/main/extensions/git/src/repository.ts) if you'd like to contribute your very own SCM provider. There are other great examples in the Marketplace such as the [SVN extension](https://marketplace.visualstudio.com/items?itemName=johnstoncode.svn-scm).
|
||||
|
||||
This documentation will help you build an extension which can make any SCM system work with VS Code.
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ A `SourceControl` is the entity responsible for populating the Source Control mo
|
|||
|
||||
You can create a new SourceControl with `vscode.scm.createSourceControl`.
|
||||
|
||||
In order to better understand how these three entities correlate with each other, let's take [Git](https://github.com/microsoft/vscode/tree/master/extensions/git) as an example. Consider the following output of `git status`:
|
||||
In order to better understand how these three entities correlate with each other, let's take [Git](https://github.com/microsoft/vscode/tree/main/extensions/git) as an example. Consider the following output of `git status`:
|
||||
|
||||
```bash
|
||||
vsce master* → git status
|
||||
|
|
@ -182,7 +182,7 @@ You can combine this API with the [`registerTextDocumentContentProvider` method
|
|||
To learn more about VS Code extensibility model, try these topics:
|
||||
|
||||
- [SCM API Reference](/api/references/vscode-api#scm) - Read the full SCM API documentation
|
||||
- [Git Extension](https://github.com/microsoft/vscode/tree/master/extensions/git) - Learn by reading the Git extension implementation
|
||||
- [Git Extension](https://github.com/microsoft/vscode/tree/main/extensions/git) - Learn by reading the Git extension implementation
|
||||
- [Extension API Overview](/api) - Learn about the full VS Code extensibility model.
|
||||
- [Extension Manifest File](/api/references/extension-manifest) - VS Code package.json extension manifest file reference
|
||||
- [Contribution Points](/api/references/contribution-points) - VS Code contribution points reference
|
||||
|
|
|
|||
|
|
@ -444,7 +444,7 @@ If your view can be empty, or if you want to add Welcome content to another exte
|
|||
|
||||
|
||||
|
||||
Links are supported in Welcome content. By convention, a link on a line by itself is a button. Each Welcome content can also contain a `when` clause. For more examples, see the [built-in Git extension](https://github.com/microsoft/vscode/tree/master/extensions/git).
|
||||
Links are supported in Welcome content. By convention, a link on a line by itself is a button. Each Welcome content can also contain a `when` clause. For more examples, see the [built-in Git extension](https://github.com/microsoft/vscode/tree/main/extensions/git).
|
||||
|
||||
## TreeDataProvider
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ MetaDescription: Visual Studio Code has a rich extension API. Learn how to creat
|
|||
|
||||
# Extension API
|
||||
|
||||
Visual Studio Code is built with extensibility in mind. From the UI to the editing experience, almost every part of VS Code can be customized and enhanced through the Extension API. In fact, many core features of VS Code are built as [extensions](https://github.com/microsoft/vscode/tree/master/extensions) and use the same Extension API.
|
||||
Visual Studio Code is built with extensibility in mind. From the UI to the editing experience, almost every part of VS Code can be customized and enhanced through the Extension API. In fact, many core features of VS Code are built as [extensions](https://github.com/microsoft/vscode/tree/main/extensions) and use the same Extension API.
|
||||
|
||||
This documentation describes:
|
||||
|
||||
|
|
|
|||
|
|
@ -44,8 +44,8 @@ A **language service** is a library that implements [programmatic language featu
|
|||
|
||||
Here's an outline of VS Code's HTML support:
|
||||
|
||||
- The built-in [html extension](https://github.com/microsoft/vscode/tree/master/extensions/html) only provides syntax highlighting and language configuration for HTML.
|
||||
- The built-in [html-language-features extension](https://github.com/microsoft/vscode/tree/master/extensions/html-language-features) includes an HTML Language Server to offer programmatic language features for HTML.
|
||||
- The built-in [html extension](https://github.com/microsoft/vscode/tree/main/extensions/html) only provides syntax highlighting and language configuration for HTML.
|
||||
- The built-in [html-language-features extension](https://github.com/microsoft/vscode/tree/main/extensions/html-language-features) includes an HTML Language Server to offer programmatic language features for HTML.
|
||||
- The HTML Language Server uses [vscode-html-languageservice](https://github.com/microsoft/vscode-html-languageservice) to support HTML.
|
||||
- The CSS Language Server uses [vscode-css-languageservice](https://github.com/microsoft/vscode-css-languageservice) to support CSS in HTML.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,13 +9,13 @@ MetaDescription: Learn how to write a Language Extension (plug-in) to add suppor
|
|||
|
||||
# Language Extensions Overview
|
||||
|
||||
Visual Studio Code provides smart editing features for different programming languages through Language Extensions. VS Code doesn't provide built-in language support but offers a set of APIs that enable rich language features. For example, it has a bundled [HTML](https://github.com/microsoft/vscode/tree/master/extensions/html) extension that allows VS Code to show syntax highlighting for HTML files. Similarly, when you type `console.` and `log` shows up in IntelliSense, it is the [Typescript Language Features](https://github.com/microsoft/vscode/tree/master/extensions/typescript-language-features) extension at work.
|
||||
Visual Studio Code provides smart editing features for different programming languages through Language Extensions. VS Code doesn't provide built-in language support but offers a set of APIs that enable rich language features. For example, it has a bundled [HTML](https://github.com/microsoft/vscode/tree/main/extensions/html) extension that allows VS Code to show syntax highlighting for HTML files. Similarly, when you type `console.` and `log` shows up in IntelliSense, it is the [Typescript Language Features](https://github.com/microsoft/vscode/tree/main/extensions/typescript-language-features) extension at work.
|
||||
|
||||
Language features can be roughly put into two categories:
|
||||
|
||||
## Declarative language features
|
||||
|
||||
Declarative language features are defined in configuration files. Examples include [html](https://github.com/microsoft/vscode/tree/master/extensions/html), [css](https://github.com/microsoft/vscode/tree/master/extensions/css) and [typescript-basic](https://github.com/microsoft/vscode/tree/master/extensions/typescript-basics) extensions bundled with VS Code, which offer a subset of the following Declarative Language Features:
|
||||
Declarative language features are defined in configuration files. Examples include [html](https://github.com/microsoft/vscode/tree/main/extensions/html), [css](https://github.com/microsoft/vscode/tree/main/extensions/css) and [typescript-basic](https://github.com/microsoft/vscode/tree/main/extensions/typescript-basics) extensions bundled with VS Code, which offer a subset of the following Declarative Language Features:
|
||||
|
||||
- Syntax highlighting
|
||||
- Snippet completion
|
||||
|
|
@ -35,7 +35,7 @@ We have three guides for writing Language Extensions that provide Declarative La
|
|||
## Programmatic language features
|
||||
|
||||
Programmatic Language Features include auto completion, error checking, and jump to definition. These features are often powered by a Language Server, a program that analyzes your project to provide the dynamic features.
|
||||
One example is the [`typescript-language-features`](https://github.com/microsoft/vscode/tree/master/extensions/typescript-language-features) extension bundled in VS Code. It utilizes the [TypeScript Language Service](https://github.com/microsoft/TypeScript/wiki/Using-the-Language-Service-API) to offer Programmatic Language Features such as:
|
||||
One example is the [`typescript-language-features`](https://github.com/microsoft/vscode/tree/main/extensions/typescript-language-features) extension bundled in VS Code. It utilizes the [TypeScript Language Service](https://github.com/microsoft/TypeScript/wiki/Using-the-Language-Service-API) to offer Programmatic Language Features such as:
|
||||
|
||||
- Hover information ([`vscode.languages.registerHoverProvider`](/api/references/vscode-api#languages.registerHoverProvider))
|
||||
- Auto completion ([`vscode.languages.registerCompletionItemProvider`](/api/references/vscode-api#languages.registerCompletionItemProvider))
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ MetaDescription: Visual Studio Code extensions (plug-in) API Reference.
|
|||
|
||||
## API namespaces and classes
|
||||
|
||||
This listing is compiled from the [`vscode.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts) file from the VS Code repository.
|
||||
This listing is compiled from the [`vscode.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts) file from the VS Code repository.
|
||||
|
||||
## authentication
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ MetaDescription: Visual Studio Code extensions (plug-in) API Reference.
|
|||
|
||||
## API namespaces and classes
|
||||
|
||||
This listing is compiled from the [`vscode.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts) file from the VS Code repository.
|
||||
This listing is compiled from the [`vscode.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts) file from the VS Code repository.
|
||||
|
||||
{$ Content $}
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Recently, GitHub introduced the ability to [add reactions to issues](https://git
|
|||
|
||||
As a result, we are "retiring" the [VS Code User Voice site](https://visualstudio.uservoice.com/forums/293070-visual-studio-code) and asking the community to submit and vote on issues in GitHub. To ease the transition, we’ve decided to migrate the current [top 50 User Voice requests](https://github.com/microsoft/vscode/issues/10715), as of 08/18/2016, to GitHub. We will triage these requests and migrate them to the appropriate repositories. If a feature request is more closely aligned with an extension and not the core VS Code product, we’ll move the request to an existing extension's repository or label it as an ["*extension-candidate"](https://github.com/microsoft/vscode/labels/*extension-candidate).
|
||||
|
||||
If your request is not on this list or if you have a new request, please open a new GitHub issue following these [guidelines](https://github.com/microsoft/vscode/blob/master/CONTRIBUTING.md). After you create an issue, we will run it through our [issue tracking](https://github.com/microsoft/vscode/wiki/Issue-Tracking) workflow. The inbox tracker for the week assigns your issue to the team member who owns the relevant area of code. The owner will then assign the correct labels and ask for more information if necessary. During milestone planning, we review the open issues and assign the ones we plan to work on to a milestone.
|
||||
If your request is not on this list or if you have a new request, please open a new GitHub issue following these [guidelines](https://github.com/microsoft/vscode/blob/main/CONTRIBUTING.md). After you create an issue, we will run it through our [issue tracking](https://github.com/microsoft/vscode/wiki/Issue-Tracking) workflow. The inbox tracker for the week assigns your issue to the team member who owns the relevant area of code. The owner will then assign the correct labels and ask for more information if necessary. During milestone planning, we review the open issues and assign the ones we plan to work on to a milestone.
|
||||
|
||||
Thank you again for your continuing feedback and hopefully this change will let us be more responsive and ultimately deliver more of the experiences you want and need in VS Code.
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ Special thanks to [Steve Lombardi](https://github.com/smlombardi), [Jens Hausdor
|
|||
|
||||
Do you miss any features of the old Emmet? Having trouble using the new Emmet? Feel free to create an GitHub [issue](https://github.com/microsoft/vscode/issues) and we will do our best to help you out.
|
||||
|
||||
It is also easier than ever to contribute to Emmet in VS Code as it is now an extension. The [emmet folder](https://github.com/microsoft/vscode/tree/master/extensions/emmet) in the VS Code GitHub repo has all the source code you need to get started.
|
||||
It is also easier than ever to contribute to Emmet in VS Code as it is now an extension. The [emmet folder](https://github.com/microsoft/vscode/tree/main/extensions/emmet) in the VS Code GitHub repo has all the source code you need to get started.
|
||||
|
||||
Happy Coding!
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ One of my responsibilities as a developer on the Visual Studio Code team is to m
|
|||
|
||||
Like any other open-source project, we need to have the right tooling and capabilities to receive, triage, and address as many code contributions as possible. This rings especially true in the developer tools universe, in which end users are developers themselves: they are a passionate, hard-working, and very effective group. As of this blog post, we have [148 open PRs as well as 3,482 closed ones](https://github.com/microsoft/vscode/pulls), which sets an average of ~3 PRs/day given the 3-year project lifespan so far. It is important that we are well equipped for handling this scale of contributions, not only to keep the project development healthy but also to help give other open-source projects an example of how to operate at this scale. Part of how we do this is by streamlining our workflow by [bringing the PR experience into the editor](/blogs/2018/09/10/introducing-github-pullrequests), but CI is the other important part of handling contributions at scale.
|
||||
|
||||
Up until very recently, we relied on the OSS community's default choices for public continuous integration: [Travis CI](https://travis-ci.org/) for our Linux and macOS builds and [AppVeyor](https://www.appveyor.com/) for Windows. Additionally, we used [Coveralls](https://coveralls.io/) to provide detailed test coverage reports. These services provide quality reports for PRs and code branches on our public repository, as they automate [compilation](https://github.com/microsoft/vscode/blob/master/build/lib/compilation.ts), run [code hygiene checks](https://github.com/microsoft/vscode/blob/master/build/gulpfile.hygiene.js) and [execute several test](https://github.com/microsoft/vscode/tree/master/test) suites, all of which is essential in order to maintain quality in a distributed team with lots of incoming contributions. This combination of services requires the understanding and maintenance of at least 3 different systems, each with its own special file formats, syntax, quirks, limitations, etc.
|
||||
Up until very recently, we relied on the OSS community's default choices for public continuous integration: [Travis CI](https://travis-ci.org/) for our Linux and macOS builds and [AppVeyor](https://www.appveyor.com/) for Windows. Additionally, we used [Coveralls](https://coveralls.io/) to provide detailed test coverage reports. These services provide quality reports for PRs and code branches on our public repository, as they automate [compilation](https://github.com/microsoft/vscode/blob/main/build/lib/compilation.ts), run [code hygiene checks](https://github.com/microsoft/vscode/blob/main/build/gulpfile.hygiene.js) and [execute several test](https://github.com/microsoft/vscode/tree/main/test) suites, all of which is essential in order to maintain quality in a distributed team with lots of incoming contributions. This combination of services requires the understanding and maintenance of at least 3 different systems, each with its own special file formats, syntax, quirks, limitations, etc.
|
||||
|
||||
## Adopting Azure Pipelines
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ We've also built a chat bot which hooks up to [Azure Pipeline's REST API](https:
|
|||
|
||||
My next task will be to take advantage of [code coverage reports](https://docs.microsoft.com/azure/devops/pipelines/tasks/test/publish-code-coverage-results) in order to get a better end-to-end CI flow than we had with the previous tool mix.
|
||||
|
||||
Having made the jump to Azure Pipelines has proved to be a big success for us. Overall code quality is easier to reason about now since builds aren't scattered all around. We have also consolidated the number and format of our [build definition files](https://github.com/microsoft/vscode/blob/master/build/tfs/product-build.yml). We're very happy with the change and excited about what the future holds for Azure Pipelines.
|
||||
Having made the jump to Azure Pipelines has proved to be a big success for us. Overall code quality is easier to reason about now since builds aren't scattered all around. We have also consolidated the number and format of our [build definition files](https://github.com/microsoft/vscode/blob/main/build/tfs/product-build.yml). We're very happy with the change and excited about what the future holds for Azure Pipelines.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ Build resubmissions saw a drastic improvement, since the shared agent tasks can
|
|||
|--------------|--------|-------|--------------|
|
||||
| macOS | 68s | 34s | 50% |
|
||||
|
||||
In total, we were thrilled to see a combined ~50% reduction in VS Code’s CI build times! The best news is that you can draw inspiration from [our build definitions](https://github.com/microsoft/vscode/tree/master/build/azure-pipelines) to realize build time improvements of your own.
|
||||
In total, we were thrilled to see a combined ~50% reduction in VS Code’s CI build times! The best news is that you can draw inspiration from [our build definitions](https://github.com/microsoft/vscode/tree/main/build/azure-pipelines) to realize build time improvements of your own.
|
||||
|
||||
Happy Caching,
|
||||
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ getLanguageService({
|
|||
})
|
||||
```
|
||||
|
||||
Our built-in [HTML language server](https://github.com/microsoft/vscode/tree/master/extensions/html-language-features) utilizes this API to load a curated set of Custom Data that we have collected from various sources:
|
||||
Our built-in [HTML language server](https://github.com/microsoft/vscode/tree/main/extensions/html-language-features) utilizes this API to load a curated set of Custom Data that we have collected from various sources:
|
||||
|
||||
- W3C specifications of HTML, CSS, and WAI-ARIA
|
||||
- Mozilla Developer Network
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@ To learn why Visual Studio Code, the product, has a different license than the o
|
|||
|
||||
### What is the difference between the `vscode` repository and the Microsoft Visual Studio Code distribution?
|
||||
|
||||
The [github.com/microsoft/vscode](https://github.com/microsoft/vscode) repository (`Code - OSS`) is where we develop the Visual Studio Code product. Not only do we write code and work on issues there, we also publish our roadmap and monthly iteration and endgame plans. The source code is available to everyone under a standard [MIT license](https://github.com/microsoft/vscode/blob/master/LICENSE.txt).
|
||||
The [github.com/microsoft/vscode](https://github.com/microsoft/vscode) repository (`Code - OSS`) is where we develop the Visual Studio Code product. Not only do we write code and work on issues there, we also publish our roadmap and monthly iteration and endgame plans. The source code is available to everyone under a standard [MIT license](https://github.com/microsoft/vscode/blob/main/LICENSE.txt).
|
||||
|
||||
Visual Studio Code is a distribution of the `Code - OSS` repository with Microsoft specific customizations (including source code), released under a traditional [Microsoft product license](https://code.visualstudio.com/License/).
|
||||
|
||||
|
|
@ -244,6 +244,6 @@ The easiest way to investigate delays in your startup file is to:
|
|||
|
||||
## Technical Support
|
||||
|
||||
You can ask questions and search for answers on [Stack Overflow](https://stackoverflow.com/questions/tagged/vscode) and enter issues and feature requests directly in our [GitHub repository](https://github.com/microsoft/vscode/blob/master/CONTRIBUTING.md).
|
||||
You can ask questions and search for answers on [Stack Overflow](https://stackoverflow.com/questions/tagged/vscode) and enter issues and feature requests directly in our [GitHub repository](https://github.com/microsoft/vscode/blob/main/CONTRIBUTING.md).
|
||||
|
||||
If you'd like to contact a professional support engineer, you can open a ticket with the [Microsoft assisted support team](https://support.microsoft.com/assistedsupportproducts).
|
||||
|
|
|
|||
|
|
@ -156,7 +156,7 @@ You can add menu items to these groups or add new groups of menu items in betwee
|
|||
|
||||
### DocumentLinkProvider API
|
||||
|
||||
VS Code has a built in link detector that finds `http`, `https`, and `file` links to make them clickable in the editor. We have added new API that allows extension writers to add custom link detection logic. Implement a `DocumentLinkProvider` and use the [`registerDocumentLinkProvider`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3814) function to register it with the editor.
|
||||
VS Code has a built in link detector that finds `http`, `https`, and `file` links to make them clickable in the editor. We have added new API that allows extension writers to add custom link detection logic. Implement a `DocumentLinkProvider` and use the [`registerDocumentLinkProvider`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L3814) function to register it with the editor.
|
||||
|
||||
### Debug Extension Authoring: Additions to the Debug Protocol
|
||||
|
||||
|
|
|
|||
|
|
@ -273,7 +273,7 @@ Please note the following limitations:
|
|||
- Contributed tasks can only be executed in the new terminal runner. To enable the terminal runner, add `"version": "2.0.0"` to your `tasks.json` file.
|
||||
- The task API is currently in proposed state.
|
||||
|
||||
For an example of how to use the API, please refer to VS Code's [gulp extension](https://github.com/microsoft/vscode/tree/master/extensions/gulp) or the proposed API [file](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts)
|
||||
For an example of how to use the API, please refer to VS Code's [gulp extension](https://github.com/microsoft/vscode/tree/main/extensions/gulp) or the proposed API [file](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts)
|
||||
|
||||
## Languages
|
||||
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ We are very excited about the possibilities of this API and expect more extensio
|
|||
|
||||
### Git
|
||||
|
||||
There has been a lot of progress improving the [Git extension](https://github.com/microsoft/vscode/tree/master/extensions/git) inside VS Code. This Git integration goes through the same [extension points](https://code.visualstudio.com/docs/extensionAPI/api-scm) as third-party SCM providers.
|
||||
There has been a lot of progress improving the [Git extension](https://github.com/microsoft/vscode/tree/main/extensions/git) inside VS Code. This Git integration goes through the same [extension points](https://code.visualstudio.com/docs/extensionAPI/api-scm) as third-party SCM providers.
|
||||
|
||||
**Note:** Starting in June, the legacy git integration will be completely removed. Until then, you can still revert back to it using the **SCM: Enable Legacy Git** command.
|
||||
|
||||
|
|
|
|||
|
|
@ -271,7 +271,7 @@ To enable the tasks preview, set the `version` attribute to `"2.0.0"` :
|
|||
}
|
||||
```
|
||||
|
||||
With version 2.0.0 enabled, the tasks from different task runners like Gulp or Grunt are automatically detected and you can run them with the `Run Task` command. Tasks are currently auto detected from the task runners Gulp, Grunt, Jake, and from the scripts section in `package.json` files. We will provide an API so that you can contribute task detection for other task runners. This API has been further polished during this iteration, but we left in the proposed state for this release (see [vscode.proposed.d.ts](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts#L13)).
|
||||
With version 2.0.0 enabled, the tasks from different task runners like Gulp or Grunt are automatically detected and you can run them with the `Run Task` command. Tasks are currently auto detected from the task runners Gulp, Grunt, Jake, and from the scripts section in `package.json` files. We will provide an API so that you can contribute task detection for other task runners. This API has been further polished during this iteration, but we left in the proposed state for this release (see [vscode.proposed.d.ts](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts#L13)).
|
||||
|
||||
The task selection dialog now shows you both tasks that you have configured in the `tasks.json` file and tasks that where automatically detected. For example, in a workspace with a gulp file defining a `build` and a `watch` task and a `tasks.json` file that defines a `Deploy` task, the task selection dialog looks as follows:
|
||||
|
||||
|
|
|
|||
|
|
@ -308,7 +308,7 @@ and the `"build"` task comes from a gulp file you now need to change this to:
|
|||
```
|
||||
If you are unsure how the task name looks like execute **Run Task...** from the global **Tasks** menu and use the label presented in the list of tasks.
|
||||
|
||||
We also released the tasks API. If you want to provide task detection for your programming language, you should have a look at the [API](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L4790-L4791) and at one of the VS Code task detection extensions like [npm scripts autodetect](https://github.com/microsoft/vscode/blob/master/extensions/npm/src/main.ts).
|
||||
We also released the tasks API. If you want to provide task detection for your programming language, you should have a look at the [API](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L4790-L4791) and at one of the VS Code task detection extensions like [npm scripts autodetect](https://github.com/microsoft/vscode/blob/main/extensions/npm/src/main.ts).
|
||||
|
||||
## Debugging
|
||||
|
||||
|
|
@ -624,11 +624,11 @@ The [initial API](https://github.com/microsoft/vscode/issues/28234) covers the l
|
|||
* `createDebugSession` for starting a debug session based on an in-memory launch configuration.
|
||||
* An `onDidTerminateDebugSession` event which indicates that a debug session has terminated.
|
||||
|
||||
> **Note:** Currently this API is proposed, so in order to use it you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** Currently this API is proposed, so in order to use it you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
### New Task API
|
||||
|
||||
If you want to provide task detection for your programming language, you can now use the official task API. Have a look at the [API](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L4790-L4791) and at one of the VS Code task detection extensions like [npm scripts autodetect](https://github.com/microsoft/vscode/blob/master/extensions/npm/src/main.ts).
|
||||
If you want to provide task detection for your programming language, you can now use the official task API. Have a look at the [API](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L4790-L4791) and at one of the VS Code task detection extensions like [npm scripts autodetect](https://github.com/microsoft/vscode/blob/main/extensions/npm/src/main.ts).
|
||||
|
||||
### Debug Adapter Protocol
|
||||
|
||||
|
|
@ -768,7 +768,7 @@ export interface WorkspaceConfiguration2 extends WorkspaceConfiguration {
|
|||
"enableProposedApi": true
|
||||
```
|
||||
|
||||
Also, copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file from our repository to your project. Including this file in your project enables type-checking and IntelliSense.
|
||||
Also, copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file from our repository to your project. Including this file in your project enables type-checking and IntelliSense.
|
||||
|
||||
As the API is in the proposed state, it is still being refined and breaking changes are likely to happen. For that reason, we don't support publishing extensions that use proposed APIs. However we do want extension writers, the clients of the extension API, to help us define how the final API should look and what it should support. Don't be shy with feedback!
|
||||
|
||||
|
|
|
|||
|
|
@ -296,7 +296,7 @@ Currently a debugger extension can contribute the "hook"-like commands `initialC
|
|||
|
||||
The new API centers around a `DebugConfigurationProvider` which is registered for a specifc debug type (which itself is contributed via a `debuggers` contribution as before). Whenever VS Code needs the initial debug configurations for a newly created launch.json it calls `provideDebugConfigurations` on the registered `DebugConfigurationProvider`s. A method `resolveDebugConfiguration` is called by VS Code when a new debug session is started. The implementation of `resolveDebugConfiguration` can "massage" the passed debug configuration by filling in missing values or by adding/changing/removing attributes.
|
||||
|
||||
> **Note:** Currently this API is proposed, so in order to use it you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** Currently this API is proposed, so in order to use it you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
**Command `vscode.startDebug` is deprecated**
|
||||
|
||||
|
|
|
|||
|
|
@ -366,7 +366,7 @@ window.createTerminal({
|
|||
|
||||
With the introduction of a proper `vscode.debug.console.append(...)` API in the October release, it is no longer necessary to use the `debug.logToDebugConsole` command to append text to the debug console. Due to that we are deprecating the `debug.logToDebugConsole` command and plan to drop support for it in the future. If it is difficult for you to move off this feature, please speak up by commenting [here](https://github.com/microsoft/vscode/issues/34700).
|
||||
|
||||
> **Note:** Currently this API is proposed, so in order to use it you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** Currently this API is proposed, so in order to use it you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
**Command `vscode.startDebug` has been removed**
|
||||
|
||||
|
|
|
|||
|
|
@ -336,7 +336,7 @@ Please note that accessing breakpoints initially returns an empty array but trig
|
|||
|
||||
The different types of breakpoints are represented as different subclasses of `Breakpoint`. Currently supported are `SourceBreakpoint` and `FunctionBreakpoint`. Use an `instanceof` check to determine the concrete type.
|
||||
|
||||
> **Note:** Currently this API is proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** Currently this API is proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
**Output text on Debug Console**
|
||||
|
||||
|
|
|
|||
|
|
@ -704,7 +704,7 @@ vscode.window.createTerminal({
|
|||
|
||||
In this milestone, we've continued work on the breakpoints debug API. It is now possible to [add and remove](https://github.com/microsoft/vscode/blob/7636a7d6f7d2749833f783e94fd3d48d6a1791cb/src/vs/vscode.proposed.d.ts#L282-L292) `SourceBreakpoints` and `FunctionBreakpoints`.
|
||||
|
||||
> **Note:** The breakpoints API is still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** The breakpoints API is still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
**new `DebugConfigurationProvider.debugAdapterExecutable` replaces `adapterExecutableCommand` commands**
|
||||
|
||||
|
|
@ -729,7 +729,7 @@ These [lines of code](https://github.com/microsoft/vscode-mock-debug/blob/042d19
|
|||
|
||||
This milestone we added new proposed extension APIs for two areas. We plan to add these APIs to stable in a future milestone once we are confident enough with them. We welcome any feedback on how they work for your extension.
|
||||
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
### Extension logging
|
||||
|
||||
|
|
|
|||
|
|
@ -369,13 +369,13 @@ The issue bot and the Issue Reporter UI run the new issue through duplicate dete
|
|||
|
||||
### Issue bot configuration by development phase
|
||||
|
||||
The issue bot changes its configuration depending on the current development phase (development, release, etc.). The change between development phases is set up ahead of time in the vscode repository at `.github/calendar.yml` ([example](https://github.com/microsoft/vscode/blob/master/.github/calendar.yml)).
|
||||
The issue bot changes its configuration depending on the current development phase (development, release, etc.). The change between development phases is set up ahead of time in the vscode repository at `.github/calendar.yml` ([example](https://github.com/microsoft/vscode/blob/main/.github/calendar.yml)).
|
||||
|
||||
## Proposed Extension APIs
|
||||
|
||||
This milestone we added several new proposed extension APIs. We plan to add these APIs to stable in a future milestone once we are confident enough with them. We welcome any feedback on how they work for your extension.
|
||||
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
### Folding
|
||||
|
||||
|
|
|
|||
|
|
@ -495,7 +495,7 @@ See the `QuickPickOptions.canPickMany` option and the `QuickPickItem.picked` fla
|
|||
|
||||
This milestone we added several new proposed extension APIs. We plan to add these APIs to stable in a future milestone once we are confident enough with them. We welcome any feedback on how they work for your extension.
|
||||
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
### Folding Provider API
|
||||
|
||||
|
|
@ -532,7 +532,7 @@ There is now a new task API which supports:
|
|||
* Terminate a running task.
|
||||
* Listen on task start and end events.
|
||||
|
||||
The proposed API can be found [here](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts#L653)
|
||||
The proposed API can be found [here](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts#L653)
|
||||
|
||||
The new API also supports executing tasks without previously returning them via a task provider. The example below executes a simple `echo` task.
|
||||
|
||||
|
|
|
|||
|
|
@ -438,7 +438,7 @@ If you want your settings to be applied at application level and not get overrid
|
|||
|
||||
This milestone we added several new proposed extension APIs. We plan to add these APIs to stable in a future milestone once we are confident enough with them. We welcome any feedback on how they work for your extension.
|
||||
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
### Integrated Terminal API
|
||||
|
||||
|
|
|
|||
|
|
@ -445,7 +445,7 @@ We've noticed that some extensions written in TypeScript are still using the old
|
|||
|
||||
This milestone we added new proposed extension APIs. We plan to add these APIs to stable in a future milestone once we are confident enough with them. We welcome any feedback on how they work for your extension.
|
||||
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
> **Note:** These APIs are still proposed, so in order to use it, you must opt into it by adding a `"enableProposedApi": true` to `package.json` and you'll have to copy the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the `enableProposedApi` attribute.
|
||||
|
||||
### Prepare for Outline view
|
||||
|
||||
|
|
@ -488,7 +488,7 @@ Meanwhile, Vetur now has End-To-End test coverage and centralized file system ac
|
|||
|
||||
## Engineering
|
||||
|
||||
We moved our [continuous integration builds](https://aka.ms/vscode-builds) over to our friends at [Azure DevOps](https://azure.microsoft.com/services/devops/) (👋 shout out to [@chrisrpatterson](https://github.com/chrisrpatterson) & [@lszomoru](https://github.com/lszomoru) for their ongoing support). This was only possible given the DevOps team's work on [public projects](https://devblogs.microsoft.com/devops/vsts-public-projects-limited-preview), as well as several other features. Azure DevOps allows us to have a [single YAML based build definition](https://github.com/microsoft/vscode/blob/master/build/tfs/continuous-build.yml) which targets all our three major platforms: Windows, macOS and Linux.
|
||||
We moved our [continuous integration builds](https://aka.ms/vscode-builds) over to our friends at [Azure DevOps](https://azure.microsoft.com/services/devops/) (👋 shout out to [@chrisrpatterson](https://github.com/chrisrpatterson) & [@lszomoru](https://github.com/lszomoru) for their ongoing support). This was only possible given the DevOps team's work on [public projects](https://devblogs.microsoft.com/devops/vsts-public-projects-limited-preview), as well as several other features. Azure DevOps allows us to have a [single YAML based build definition](https://github.com/microsoft/vscode/blob/main/build/tfs/continuous-build.yml) which targets all our three major platforms: Windows, macOS and Linux.
|
||||
|
||||
[](https://aka.ms/vscode-builds)
|
||||
|
||||
|
|
|
|||
|
|
@ -605,7 +605,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
Order:
|
||||
Order:
|
||||
TOCTitle: July 2018
|
||||
PageTitle: Visual Studio Code July 2018
|
||||
MetaDescription: See what is new in the Visual Studio Code July 2018 Release (1.26)
|
||||
|
|
@ -507,7 +507,7 @@ export namespace window {
|
|||
|
||||
It comes with a `onUri` activation event which activates an extension whenever a URI directed towards itself is opened by the operating system.
|
||||
|
||||
Refer to the Git extension's [GitProtocolHandler](https://github.com/microsoft/vscode/blob/master/extensions/git/src/protocolHandler.ts) for a reference implementation.
|
||||
Refer to the Git extension's [GitProtocolHandler](https://github.com/microsoft/vscode/blob/main/extensions/git/src/protocolHandler.ts) for a reference implementation.
|
||||
|
||||
### Node.js update
|
||||
|
||||
|
|
@ -525,7 +525,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -279,7 +279,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -408,7 +408,7 @@ In this release, we updated from Electron 2.0.7 to 2.0.9. Most notably, this all
|
|||
|
||||
### Diagnostic error codes
|
||||
|
||||
Since diagnostic error codes are now surfaced in [Problems panel](#problems-panel), it is no longer necessary for extensions to add error codes to the [`Diagnostic.message`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L4074) property.
|
||||
Since diagnostic error codes are now surfaced in [Problems panel](#problems-panel), it is no longer necessary for extensions to add error codes to the [`Diagnostic.message`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L4074) property.
|
||||
|
||||
### Better configuration when clauses
|
||||
|
||||
|
|
@ -457,7 +457,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
Order:
|
||||
Order:
|
||||
TOCTitle: October 2018
|
||||
PageTitle: Visual Studio Code October 2018
|
||||
MetaDescription: See what is new in the Visual Studio Code October 2018 Release (1.29)
|
||||
|
|
@ -344,7 +344,7 @@ During this milestone, we continued to explore bundling Electron 3.0.0 into VS C
|
|||
|
||||
This milestone, we also [started work](https://github.com/microsoft/vscode/issues/60565) to enable TypeScript's [strict null checks](https://www.typescriptlang.org/docs/handbook/basic-types.html#null-and-undefined) in the core VS Code source. Strict null checks help catch many common programming mistakes and make the intent of the programmer more explicit. We've seen clear benefits using strict null checks for VS Code's built-in extensions.
|
||||
|
||||
Since VS Code's [core source](https://github.com/microsoft/vscode/tree/master/src) contains several thousand files, we are adopting strict null checking incrementally. We started by strict null checking files that have no imports and are now iteratively enabling strict null checks in files that only import other strict null checked files. This will continue until the entire code base is converted.
|
||||
Since VS Code's [core source](https://github.com/microsoft/vscode/tree/main/src) contains several thousand files, we are adopting strict null checking incrementally. We started by strict null checking files that have no imports and are now iteratively enabling strict null checks in files that only import other strict null checked files. This will continue until the entire code base is converted.
|
||||
|
||||
Enabling strict null checks is a major engineering effort but we think the payoff in terms of source code and product quality will be worth it. You can track our strict null checking progress [here](https://github.com/microsoft/vscode/issues/60565).
|
||||
|
||||
|
|
@ -443,7 +443,7 @@ There are new theme colors:
|
|||
|
||||
### Git extension API additions
|
||||
|
||||
The [Git extension API](https://github.com/microsoft/vscode/blob/master/extensions/git/src/api/git.d.ts) has been updated to expose details on the actual [changes](https://github.com/microsoft/vscode/blob/ae5b8fb1978bfb595ec4821af0d61d32d80a177c/extensions/git/src/api/git.d.ts#L80:L91) each repository has.
|
||||
The [Git extension API](https://github.com/microsoft/vscode/blob/main/extensions/git/src/api/git.d.ts) has been updated to expose details on the actual [changes](https://github.com/microsoft/vscode/blob/ae5b8fb1978bfb595ec4821af0d61d32d80a177c/extensions/git/src/api/git.d.ts#L80:L91) each repository has.
|
||||
|
||||
Additionally, the following methods have been exposed:
|
||||
|
||||
|
|
@ -464,7 +464,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
Order:
|
||||
Order:
|
||||
TOCTitle: November 2018
|
||||
PageTitle: Visual Studio Code November 2018
|
||||
MetaDescription: See what is new in the Visual Studio Code November 2018 Release (1.30)
|
||||
|
|
@ -592,7 +592,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -593,7 +593,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -332,7 +332,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -249,7 +249,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -145,7 +145,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
@ -193,7 +193,7 @@ If you have settings that allow users to customize an executable path and if the
|
|||
|
||||
### Rewritten filesystem provider for local files
|
||||
|
||||
Extensions have been able to provide their own filesystem implementations for custom resources ([read more here](https://code.visualstudio.com/updates/v1_23#_filesystem-providers)). However, VS Code's own implementation for local files was not implemented with the same extension APIs. This resulted in subtle differences when dealing with local file resources compared to resources coming from extensions. Over the last two milestones, we [rewrote our local file system provider](https://github.com/microsoft/vscode/blob/master/src/vs/workbench/services/files/node/diskFileSystemProvider.ts) to use the extension APIs for consistency.
|
||||
Extensions have been able to provide their own filesystem implementations for custom resources ([read more here](https://code.visualstudio.com/updates/v1_23#_filesystem-providers)). However, VS Code's own implementation for local files was not implemented with the same extension APIs. This resulted in subtle differences when dealing with local file resources compared to resources coming from extensions. Over the last two milestones, we [rewrote our local file system provider](https://github.com/microsoft/vscode/blob/main/src/vs/workbench/services/files/node/diskFileSystemProvider.ts) to use the extension APIs for consistency.
|
||||
|
||||
## New documentation
|
||||
|
||||
|
|
|
|||
|
|
@ -227,7 +227,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -339,7 +339,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -408,7 +408,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -455,7 +455,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -357,7 +357,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
|
|
|
|||
|
|
@ -455,7 +455,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -639,7 +639,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
@ -688,7 +688,7 @@ If your extension uses Code Actions, please [let us know](https://github.com/mic
|
|||
|
||||
We continued to work on the [custom editor proposal](https://github.com/microsoft/vscode/issues/77131) this iteration. As a reminder, custom editors are webview-based views that can be used in place of VS Code's normal text editor for specific file types. As of VS Code 1.41, Custom editors can now integrate with VS Code's Undo/Redo and Save functionality, which enables many interesting use cases including using them as visual and WYSIWYG editors.
|
||||
|
||||
You can find the current API proposal in [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts)
|
||||
You can find the current API proposal in [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts)
|
||||
and we have also put together some [very simple extension samples](https://github.com/mjbvz/vscode-experimental-webview-editor-extension) that demonstrate using custom editors for text and for binary files.
|
||||
|
||||
If you are interested in custom editors, please share your feedback on the current proposal and let us know if you would be able to implement it.
|
||||
|
|
|
|||
|
|
@ -779,7 +779,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -634,7 +634,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -528,7 +528,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -497,7 +497,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -611,13 +611,13 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
### Git extension API
|
||||
|
||||
The built-in Git extension [offers an API](https://github.com/microsoft/vscode/blob/master/extensions/git/src/api/git.d.ts) for extensions to use. The existing API exposed a way to get `log` results for a `Repository`. The updated API will now let `log` be constrained by a `path`.
|
||||
The built-in Git extension [offers an API](https://github.com/microsoft/vscode/blob/main/extensions/git/src/api/git.d.ts) for extensions to use. The existing API exposed a way to get `log` results for a `Repository`. The updated API will now let `log` be constrained by a `path`.
|
||||
|
||||
```typescript
|
||||
export interface LogOptions {
|
||||
|
|
|
|||
|
|
@ -464,7 +464,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -273,7 +273,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -406,7 +406,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
Note that 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -291,7 +291,7 @@ For the [VIM extension](https://marketplace.visualstudio.com/items?itemName=vsco
|
|||
|
||||
### Powerful Completion Items
|
||||
|
||||
The [`Completion Item`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L2246) now supports additional text edits and an additional command.
|
||||
The [`Completion Item`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L2246) now supports additional text edits and an additional command.
|
||||
|
||||
With those, you can do rich things like:
|
||||
|
||||
|
|
|
|||
|
|
@ -350,7 +350,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -296,7 +296,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -715,7 +715,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -422,7 +422,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
* You must use Insiders because proposed APIs change frequently.
|
||||
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts) file into your project's source location.
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ Often you have a set of extensions that makes working with a particular workspac
|
|||
|
||||
You can create this file using the **Extensions: Configure Workspace Recommended Extensions** command.
|
||||
|
||||
For example, this is the `extensions.json` file that we use for the [vscode workspace](https://github.com/microsoft/vscode/blob/master/.vscode/extensions.json):
|
||||
For example, this is the `extensions.json` file that we use for the [vscode workspace](https://github.com/microsoft/vscode/blob/main/.vscode/extensions.json):
|
||||
|
||||
```json
|
||||
{
|
||||
|
|
|
|||
|
|
@ -301,11 +301,11 @@ For example:
|
|||
|
||||
### onDidChangeVisibleTextEditors event
|
||||
|
||||
We added an [`onDidChangeVisibleTextEditors`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L3383) event which fires whenever the list of visible editors changes.
|
||||
We added an [`onDidChangeVisibleTextEditors`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L3383) event which fires whenever the list of visible editors changes.
|
||||
|
||||
### Update Now: Using latest vscode.d.ts
|
||||
|
||||
As ever, the latest and greatest version of our extension API is defined in the [`vscode.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts) file.
|
||||
As ever, the latest and greatest version of our extension API is defined in the [`vscode.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts) file.
|
||||
>**Note:** when you update your extension to use an API version 1.7.0 or newer, make sure you use the latest version of the [vscode](https://www.npmjs.com/package/vscode)-node-module (^1.0.3) and make sure to use TypeScript 2.0.
|
||||
|
||||
Please read [here](https://code.visualstudio.com/updates/v1_6#_extension-authoring) to learn how to migrate your existing extensions to the latest vscode module.
|
||||
|
|
|
|||
|
|
@ -459,15 +459,15 @@ We have updated the type definitions in `vscode.d.ts` to explicit spell out when
|
|||
|
||||
### Snippet Completions
|
||||
|
||||
A completion item provider can now return completions that are inserted as snippet. When creating an item, make sure its `insertText` is a [`SnippetString`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L2073). When selected, the editor will go to snippet mode, allowing the have placeholders and control over the cursor position.
|
||||
A completion item provider can now return completions that are inserted as snippet. When creating an item, make sure its `insertText` is a [`SnippetString`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L2073). When selected, the editor will go to snippet mode, allowing the have placeholders and control over the cursor position.
|
||||
|
||||
### Inspect Configurations
|
||||
|
||||
With the new [`inspect`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L2825)-function you can figure out where a configuration value was defined and what it default is.
|
||||
With the new [`inspect`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L2825)-function you can figure out where a configuration value was defined and what it default is.
|
||||
|
||||
### TextDocument#getWordRangeAt
|
||||
|
||||
Ever since the text document allows to ask for a [word-range](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L221) at a given position. To know what a word is VS Code uses the [word-pattern](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts#L2714) of the respective language. That's not always good enough and therefore you can now provide a regular expression that will be used instead.
|
||||
Ever since the text document allows to ask for a [word-range](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L221) at a given position. To know what a word is VS Code uses the [word-pattern](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L2714) of the respective language. That's not always good enough and therefore you can now provide a regular expression that will be used instead.
|
||||
|
||||
### Debugger Extension Authoring
|
||||
|
||||
|
|
|
|||
|
|
@ -649,7 +649,7 @@ A new `Folder` value was added to the `CompletionItemKind` enum.
|
|||
|
||||
We have a proposed API to show progress in different places of the editor, such as the Status Bar or a view. It is still in its early stages and we are looking for feedback. To try it out, do the following:
|
||||
|
||||
* Copy [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts#L30) into your TypeScript project.
|
||||
* Copy [`vscode.proposed.d.ts`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.proposed.d.ts#L30) into your TypeScript project.
|
||||
* In the `package.json` of your extension, add `"enableProposedApi": true` to enable the proposed APIs.
|
||||
|
||||
Note that proposed APIs are only available when developing an extension but not when an extension is published to the Marketplace.
|
||||
|
|
|
|||
|
|
@ -144,7 +144,7 @@ When previewing HTML files with the `vscode.previewHtml` command, links are now
|
|||
|
||||
If you have your own JSON files and want to improve the editing experience, you can associate JSON schemas to your files. The schemas associations will be picked up by the JSON language support that ships with VS Code and you will get validations, completions and hovers for free. The schema association can be done either [by a user configuration](https://code.visualstudio.com/docs/languages/json#_json-schemas-settings) or [by an extension point](https://code.visualstudio.com/docs/extensionAPI/extension-points#_contributesjsonvalidation).
|
||||
|
||||
In some cases, you want more control, for example, you may want to provide completion support that requires a database lookup, or you want validation that cannot be expressed by a regular expression. To implement your own completion, validation, and hover support, you can use the regular VS Code APIs. To make this easier, we moved our JSON scanner and parsers to a node-module, [jsonc-parser](https://www.npmjs.com/package/jsonc-parser), that you can reuse. You can see this module in action with the dependency completion support for `package.json` and `bower.json` that is now part of the [JavaScript extension]( https://github.com/microsoft/vscode/tree/master/extensions/javascript) and for `project.json` soon to be part of the [C# extension](https://github.com/OmniSharp/omnisharp-vscode/).
|
||||
In some cases, you want more control, for example, you may want to provide completion support that requires a database lookup, or you want validation that cannot be expressed by a regular expression. To implement your own completion, validation, and hover support, you can use the regular VS Code APIs. To make this easier, we moved our JSON scanner and parsers to a node-module, [jsonc-parser](https://www.npmjs.com/package/jsonc-parser), that you can reuse. You can see this module in action with the dependency completion support for `package.json` and `bower.json` that is now part of the [JavaScript extension]( https://github.com/microsoft/vscode/tree/main/extensions/javascript) and for `project.json` soon to be part of the [C# extension](https://github.com/OmniSharp/omnisharp-vscode/).
|
||||
|
||||
### 'onDebug' Activation Event
|
||||
|
||||
|
|
|
|||
|
|
@ -252,7 +252,7 @@ For VS Code Mono debugging support, we've added an `externalConsole` attribute,
|
|||
|
||||
### API Consumption
|
||||
|
||||
When you write an extension for VS Code, you are developing it against a set of APIs that we define through a file called `vscode.d.ts`. You can see this file in our repository [here](https://github.com/microsoft/vscode/blob/master/src/vs/vscode.d.ts). This file is picked up from our TypeScript and JavaScript language service to provide you with rich validation and IntelliSense while you develop your extension.
|
||||
When you write an extension for VS Code, you are developing it against a set of APIs that we define through a file called `vscode.d.ts`. You can see this file in our repository [here](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts). This file is picked up from our TypeScript and JavaScript language service to provide you with rich validation and IntelliSense while you develop your extension.
|
||||
|
||||
As we make changes to the VS Code API between versions, `vscode.d.ts` changes and is updated and tagged from release to release. Previously, we stored the `vscode.d.ts` file within the `vscode` npm module that all extensions automatically depend on. So to update to our latest API, you would just install a newer version of the `vscode` npm module in your extension by typing `npm update vscode`.
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче