For #271167
This makes it so our built-in extensions can mostly be built using `tsc` on the command line. Previously the extensions were picking up a lot of typing info from the root `node_modules` that meant they weren't truly independent
* Split TS' AI-backed code actions into separate entries
Lets the user decide whether to add AI to their code action, which shows
intent, which is good for us to learn whether people actually want this.
Related: this should be unflagged for insiders. To do this, do I just
delete the flags?
* Stop appending a duplicate message in missingFunctionDeclaration
* Fix: quickfix was still showing Copilot-only
It's a workaround--I'm not sure of the right way to do this.
* Update to use `isAI`
* Put AI code actions after others.
* Add isAI to rest of code actions
* Remove flags for TS AI code actions
* Check for copilot-chat instead of copilot
It's possible to have copilot installed without copilot-chat.
* Fix file casing
---------
Co-authored-by: Matt Bierner <matb@microsoft.com>
* Experiment with adding ata using `@types` packages shipped in an extension
* Use own file system instead of `https`
* JS/TS type support on web
* Tsconfig needs esModuleInterop not module:nodenext
We actually want webpack to emit commonjs, but need to write ES default
imports to use node-maintainer
* fix package.json indentation
* Adding setting to disable web type acquisition
* Fix merge of yarn lock
* Fixing merge errors
* Fixing errors
* Pick up package externally
* Fixing conflicts
* Bump version
---------
Co-authored-by: Kat Marchán <kzm@zkat.tech>
Co-authored-by: Nathan Shively-Sanders <293473+sandersn@users.noreply.github.com>
* add `WorkspaceEditMetadata` and use it for `applyEdit`,
https://github.com/microsoft/vscode/issues/112109
* fix compilo in tests
* workspace edits from updating paths are marked as refactoring fyi @mjbvz
Currently extensions like TS have a dev dependency on the `"vscode"` package. This pulls in a copy of `vscode.d.ts` that we end up using instead of our local `vscode.d.ts`.
This change uses the `paths` `tsconig` option so that we use our local `vscode.d.ts` instead of the one from `node_modules`
Setup a baseline tsconfig for extensions to extend. This will help make sure thatof our built-in extensions are using the recommended settings for target and so on. it also reduces duplicated code and will make updating tsconfig settings easier
