Author: Nikola Hristov

Source/ESBuild.ts

@@ -21,7 +21,7 @@ export default {
 	outdir: `Target/${Dependency}`,
 	platform: "node",
 	target: "esnext",
-	tsconfig: `Source/Notation/${Dependency}/tsconfig${On ? "" : ".no-types"}.json`,
+	tsconfig: On ? `TypeLess/${Dependency}.json` : `tsconfig/${Dependency}.json`,
 	write: true,
 	legalComments: On ? "inline" : "none",
 	bundle: false,

Source/Typeless/Microsoft/VSCode.json Source/Typeless2/Microsoft/VSCode.jsonSource/Typeless/Microsoft/VSCode.json renamed to Source/Typeless2/Microsoft/VSCode.json

@@ -1,4 +1,3 @@
-
 # vscode-dts
 
 This is the place for the stable API and for API proposals.
@@ -9,12 +8,19 @@ This is the place for the stable API and for API proposals.
 1. add its name to your extensions `package.json#enabledApiProposals` property
 1. run `npx vscode-dts dev` to download the `d.ts` files into your project
 1. don't forget that extension using proposed API cannot be published
-1. learn more here: <https://code.visualstudio.com/api/advanced-topics/using-proposed-api>
+1. learn more here:
+   <https://code.visualstudio.com/api/advanced-topics/using-proposed-api>
 
 ## Add a new proposal
 
-1. create a _new_ file in this directory, its name must follow this pattern `vscode.proposed.[a-zA-Z]+.d.ts`
-1. creating the proposal-file will automatically update `src/vs/platform/extensions/common/extensionsApiProposals.ts` (make sure to run `npm run watch`)
+1. create a _new_ file in this directory, its name must follow this pattern
+   `vscode.proposed.[a-zA-Z]+.d.ts`
+1. creating the proposal-file will automatically update
+   `src/vs/platform/extensions/common/extensionsApiProposals.ts` (make sure to
+   run `npm run watch`)
 1. declare and implement your proposal
-1. make sure to use the `checkProposedApiEnabled` and/or `isProposedApiEnabled`-utils to enforce the API being proposed. Make sure to invoke them with your proposal's name which got generated into `extensionsApiProposals.ts`
+1. make sure to use the `checkProposedApiEnabled` and/or
+   `isProposedApiEnabled`-utils to enforce the API being proposed. Make sure to
+   invoke them with your proposal's name which got generated into
+   `extensionsApiProposals.ts`
 1. Most likely will need to add your proposed api to vscode-api-tests as well

…icrosoft/VSCode/Asset/README-E6G77BW2.md …icrosoft/VSCode/Asset/README-EW5ENTOS.mdTarget/Microsoft/VSCode/Asset/README-E6G77BW2.md renamed to Target/Microsoft/VSCode/Asset/README-EW5ENTOS.md Target/Microsoft/VSCode/Asset/README-E6G77BW2.md renamed to Target/Microsoft/VSCode/Asset/README-EW5ENTOS.md

@@ -0,0 +1,15 @@
+_Terminal contribs_ are a way of splitting out standalone terminal features into
+their own components that build upon the main terminal code. The
+`terminalContrib/` folder can only import from `terminal/`, not the other way
+around. There are eslint rules to prevent this circular dependencies.
+
+Having the entire feature and its tests in the same place makes not only the
+contrib easier to maintain and understand, but also the core terminal code as
+it's less interspersed with feature code. Sometimes it's not possible without
+bigger changes to make the feature totally standalone, in this case the goal is
+to get as close as possible.
+
+This should not be confused with the similar `ITerminalContribution` which is a
+parallel to `IEditorContribution` and is used for decorating each individual
+terminal with additional functionality. An entry in `terminalContrib/` may use
+`ITerminalContribution`s to add its features.