Author: Nikola Hristov

generators/app/templates/ext-colortheme/vsc-extension-quickstart.md

@@ -2,40 +2,40 @@
 
 ## What's in the folder
 
--   This folder contains all of the files necessary for your color theme
-    extension.
--   `package.json` - this is the manifest file that defines the location of the
-    theme file and specifies the base theme of the theme.
--   `themes/<%= themeFileName %>` - the color theme definition file.
+- This folder contains all of the files necessary for your color theme
+  extension.
+- `package.json` - this is the manifest file that defines the location of the
+  theme file and specifies the base theme of the theme.
+- `themes/<%= themeFileName %>` - the color theme definition file.
 
 ## Get up and running straight away
 
--   Press `F5` to open a new window with your extension loaded.
--   Open the color theme picker with the
-    `File > Preferences > Theme > Color Theme` menu item, or use the
-    `Preferences: Color Theme command (Ctrl+K Ctrl+T)` and pick your theme
--   Open a file that has a language associated. The languages' configured
-    grammar will tokenize the text and assign 'scopes' to the tokens. To examine
-    these scopes, invoke the `Developer: Inspect Editor Tokens and Scopes`
-    command from the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac).
+- Press `F5` to open a new window with your extension loaded.
+- Open the color theme picker with the
+  `File > Preferences > Theme > Color Theme` menu item, or use the
+  `Preferences: Color Theme command (Ctrl+K Ctrl+T)` and pick your theme
+- Open a file that has a language associated. The languages' configured grammar
+  will tokenize the text and assign 'scopes' to the tokens. To examine these
+  scopes, invoke the `Developer: Inspect Editor Tokens and Scopes` command from
+  the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac).
 
 ## Make changes
 
--   Changes to the theme file are automatically applied to the Extension
-    Development Host window.
+- Changes to the theme file are automatically applied to the Extension
+  Development Host window.
 
 ## Adopt your theme to Visual Studio Code
 
--   The token colorization is done based on standard TextMate themes. Colors are
-    matched against one or more scopes.
+- The token colorization is done based on standard TextMate themes. Colors are
+  matched against one or more scopes.
 
 To learn more about scopes and how they're used, check out the
 [`color theme`](https://code.visualstudio.com/api/extension-guides/color-theme)
 documentation.
 
 ## Install your extension
 
--   To start using your extension with Visual Studio Code copy it into the
-    `<user home>/.vscode/extensions` folder and restart Code.
--   To share your extension with the world, read on
-    HTTPS://code.visualstudio.com/docs about publishing an extension.
+- To start using your extension with Visual Studio Code copy it into the
+  `<user home>/.vscode/extensions` folder and restart Code.
+- To share your extension with the world, read on
+  HTTPS://code.visualstudio.com/docs about publishing an extension.

generators/app/templates/ext-command-js/vsc-extension-quickstart.md

@@ -2,63 +2,63 @@
 
 ## What's in the folder
 
--   This folder contains all of the files necessary for your extension.
--   `package.json` - this is the manifest file in which you declare your
-    extension and command.
-    -   The sample plugin registers a command and defines its title and command
-        name. With this information VS Code can show the command in the command
-        palette. It doesn’t yet need to load the plugin.
--   `extension.js` - this is the main file where you will provide the
-    implementation of your command.
-    -   The file exports one function, `activate`, which is called the very
-        first time your extension is activated (in this case by executing the
-        command). Inside the `activate` function we call `registerCommand`.
-    -   We pass the function containing the implementation of the command as the
-        second parameter to `registerCommand`.
+- This folder contains all of the files necessary for your extension.
+- `package.json` - this is the manifest file in which you declare your extension
+  and command.
+    - The sample plugin registers a command and defines its title and command
+      name. With this information VS Code can show the command in the command
+      palette. It doesn’t yet need to load the plugin.
+- `extension.js` - this is the main file where you will provide the
+  implementation of your command.
+    - The file exports one function, `activate`, which is called the very first
+      time your extension is activated (in this case by executing the command).
+      Inside the `activate` function we call `registerCommand`.
+    - We pass the function containing the implementation of the command as the
+      second parameter to `registerCommand`.
 
 ## Get up and running straight away
 
--   Press `F5` to open a new window with your extension loaded.
--   Run your command from the command palette by pressing (`Ctrl+Shift+P` or
-    `Cmd+Shift+P` on Mac) and typing `Hello World`.
--   Set breakpoints in your code inside `extension.js` to debug your extension.
--   Find output from your extension in the debug console.
+- Press `F5` to open a new window with your extension loaded.
+- Run your command from the command palette by pressing (`Ctrl+Shift+P` or
+  `Cmd+Shift+P` on Mac) and typing `Hello World`.
+- Set breakpoints in your code inside `extension.js` to debug your extension.
+- Find output from your extension in the debug console.
 
 ## Make changes
 
--   You can relaunch the extension from the debug toolbar after changing code in
-    `extension.js`.
--   You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with
-    your extension to load your changes.
+- You can relaunch the extension from the debug toolbar after changing code in
+  `extension.js`.
+- You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your
+  extension to load your changes.
 
 ## Explore the API
 
--   You can open the full set of our API when you open the file
-    `node_modules/@types/vscode/index.d.ts`.
+- You can open the full set of our API when you open the file
+  `node_modules/@types/vscode/index.d.ts`.
 
 ## Run tests
 
--   Install the
-    [`Extension Test Runner`](https://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
--   Open the Testing view from the activity bar and click the Run Test" button,
-    or use the hotkey `Ctrl/Cmd + ; A`
--   See the output of the test result in the Test Results view.
--   Make changes to `test/extension.test.js` or create new test files inside the
-    `test` folder.
-    -   The provided test runner will only consider files matching the name
-        pattern `**.test.js`.
-    -   You can create folders inside the `test` folder to structure your tests
-        any way you want.
+- Install the
+  [`Extension Test Runner`](https://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
+- Open the Testing view from the activity bar and click the Run Test" button, or
+  use the hotkey `Ctrl/Cmd + ; A`
+- See the output of the test result in the Test Results view.
+- Make changes to `test/extension.test.js` or create new test files inside the
+  `test` folder.
+    - The provided test runner will only consider files matching the name
+      pattern `**.test.js`.
+    - You can create folders inside the `test` folder to structure your tests
+      any way you want.
 
 ## Go further
 
--   [`Follow UX guidelines`](https://code.visualstudio.com/api/ux-guidelines/overview)
-    to create extensions that seamlessly integrate with VS Code's native
-    interface and patterns.
--   [`Publish your extension`](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)
-    on the VS Code extension marketplace.
--   Automate builds by setting up
-    [`Continuous Integration`](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).
--   Integrate to the
-    [`report issue`](https://code.visualstudio.com/api/get-started/wrapping-up#issue-reporting)
-    flow to get issue and feature requests reported by users.
+- [`Follow UX guidelines`](https://code.visualstudio.com/api/ux-guidelines/overview)
+  to create extensions that seamlessly integrate with VS Code's native interface
+  and patterns.
+- [`Publish your extension`](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)
+  on the VS Code extension marketplace.
+- Automate builds by setting up
+  [`Continuous Integration`](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).
+- Integrate to the
+  [`report issue`](https://code.visualstudio.com/api/get-started/wrapping-up#issue-reporting)
+  flow to get issue and feature requests reported by users.

generators/app/templates/ext-command-ts/vsc-extension-quickstart.md

@@ -2,68 +2,68 @@
 
 ## What's in the folder
 
--   This folder contains all of the files necessary for your extension.
--   `package.json` - this is the manifest file in which you declare your
-    extension and command.
-    -   The sample plugin registers a command and defines its title and command
-        name. With this information VS Code can show the command in the command
-        palette. It doesn’t yet need to load the plugin.
--   `src/extension.ts` - this is the main file where you will provide the
-    implementation of your command.
-    -   The file exports one function, `activate`, which is called the very
-        first time your extension is activated (in this case by executing the
-        command). Inside the `activate` function we call `registerCommand`.
-    -   We pass the function containing the implementation of the command as the
-        second parameter to `registerCommand`.
+- This folder contains all of the files necessary for your extension.
+- `package.json` - this is the manifest file in which you declare your extension
+  and command.
+    - The sample plugin registers a command and defines its title and command
+      name. With this information VS Code can show the command in the command
+      palette. It doesn’t yet need to load the plugin.
+- `src/extension.ts` - this is the main file where you will provide the
+  implementation of your command.
+    - The file exports one function, `activate`, which is called the very first
+      time your extension is activated (in this case by executing the command).
+      Inside the `activate` function we call `registerCommand`.
+    - We pass the function containing the implementation of the command as the
+      second parameter to `registerCommand`.
 
 ## Get up and running straight away
 
--   Press `F5` to open a new window with your extension loaded.
--   Run your command from the command palette by pressing (`Ctrl+Shift+P` or
-    `Cmd+Shift+P` on Mac) and typing `Hello World`.
--   Set breakpoints in your code inside `src/extension.ts` to debug your
-    extension.
--   Find output from your extension in the debug console.
+- Press `F5` to open a new window with your extension loaded.
+- Run your command from the command palette by pressing (`Ctrl+Shift+P` or
+  `Cmd+Shift+P` on Mac) and typing `Hello World`.
+- Set breakpoints in your code inside `src/extension.ts` to debug your
+  extension.
+- Find output from your extension in the debug console.
 
 ## Make changes
 
--   You can relaunch the extension from the debug toolbar after changing code in
-    `src/extension.ts`.
--   You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with
-    your extension to load your changes.
+- You can relaunch the extension from the debug toolbar after changing code in
+  `src/extension.ts`.
+- You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your
+  extension to load your changes.
 
 ## Explore the API
 
--   You can open the full set of our API when you open the file
-    `node_modules/@types/vscode/index.d.ts`.
+- You can open the full set of our API when you open the file
+  `node_modules/@types/vscode/index.d.ts`.
 
 ## Run tests
 
--   Install the
-    [`Extension Test Runner`](HTTPS://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
--   Run the "watch" task via the **Tasks: Run Task** command. Make sure this is
-    running, or tests might not be discovered.
--   Open the Testing view from the activity bar and click the Run Test" button,
-    or use the hotkey `Ctrl/Cmd + ; A`
--   See the output of the test result in the Test Results view.
--   Make changes to `src/test/extension.test.ts` or create new test files inside
-    the `test` folder.
-    -   The provided test runner will only consider files matching the name
-        pattern `**.test.ts`.
-    -   You can create folders inside the `test` folder to structure your tests
-        any way you want.
+- Install the
+  [`Extension Test Runner`](HTTPS://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
+- Run the "watch" task via the **Tasks: Run Task** command. Make sure this is
+  running, or tests might not be discovered.
+- Open the Testing view from the activity bar and click the Run Test" button, or
+  use the hotkey `Ctrl/Cmd + ; A`
+- See the output of the test result in the Test Results view.
+- Make changes to `src/test/extension.test.ts` or create new test files inside
+  the `test` folder.
+    - The provided test runner will only consider files matching the name
+      pattern `**.test.ts`.
+    - You can create folders inside the `test` folder to structure your tests
+      any way you want.
 
 ## Go further
 
--   [`Follow UX guidelines`](HTTPS://code.visualstudio.com/api/ux-guidelines/overview)
-    to create extensions that seamlessly integrate with VS Code's native
-    interface and patterns.
--   Reduce the extension size and improve the startup time by
-    [`bundling your extension`](HTTPS://code.visualstudio.com/api/working-with-extensions/bundling-extension).
--   [`Publish your extension`](HTTPS://code.visualstudio.com/api/working-with-extensions/publishing-extension)
-    on the VS Code extension marketplace.
--   Automate builds by setting up
-    [`Continuous Integration`](HTTPS://code.visualstudio.com/api/working-with-extensions/continuous-integration).
--   Integrate to the
-    [`report issue`](HTTPS://code.visualstudio.com/api/get-started/wrapping-up#issue-reporting)
-    flow to get issue and feature requests reported by users.
+- [`Follow UX guidelines`](HTTPS://code.visualstudio.com/api/ux-guidelines/overview)
+  to create extensions that seamlessly integrate with VS Code's native interface
+  and patterns.
+- Reduce the extension size and improve the startup time by
+  [`bundling your extension`](HTTPS://code.visualstudio.com/api/working-with-extensions/bundling-extension).
+- [`Publish your extension`](HTTPS://code.visualstudio.com/api/working-with-extensions/publishing-extension)
+  on the VS Code extension marketplace.
+- Automate builds by setting up
+  [`Continuous Integration`](HTTPS://code.visualstudio.com/api/working-with-extensions/continuous-integration).
+- Integrate to the
+  [`report issue`](HTTPS://code.visualstudio.com/api/get-started/wrapping-up#issue-reporting)
+  flow to get issue and feature requests reported by users.