Merge to main (#9)

* Updating display name and fixing readme img paths for marketplace.

Author: colinmoynes

README.md

@@ -1,12 +1,12 @@
 
 
-<img src="./media/readme/brand-banner.png" alt="banner" />
+<img src="media/readme/brand-banner.png" alt="banner" />
 
 # Cloudsmith Visual Studio Code Extension
 
-<img src="./media/readme/overview.gif" alt="overview" width="600"/>
+<img src="media/readme/overview.gif" alt="overview" width="600"/>
 
-<img src="./media/readme/brand-card.png" alt="brand-card" />
+<img src="media/readme/brand-card.png" alt="brand-card" />
 
 ## Installation
 
@@ -35,7 +35,7 @@ code-insiders --install-extension cloudsmith-x-x-x.vsix
 ### Connect
 After installing, to connect to your Cloudsmith instance, you need to configure either your Personal API Key or a Service Account Token. Click on the `key` icon from the view menu and enter your credential into the input box. To connect press the `connect` or `refresh` icons. 
 
-<img src="./media/readme/configure.gif" alt="configure" width="1000"/>
+<img src="media/readme/configure.gif" alt="configure" width="1000"/>
 
 ### Settings
 
@@ -47,7 +47,7 @@ A range of settings are configurable for the extension. See Overview for usage o
 * Use Legacy Web App - URLs to Cloudsmith packages will use the legacy Web App instead. 
 
 
-<img src="./media/readme/settings.gif" alt="settings" width="1000"/>
+<img src="media/readme/settings.gif" alt="settings" width="1000"/>
 
 
 ## Overview
@@ -61,7 +61,7 @@ The Cloudsmith extension contributes a Cloudsmith view to VS Code. The Cloudsmit
 By default the extension returns individual packages. You can display them as [package groups](https://help.cloudsmith.io/docs/package-groups) instead. 
 
 
-<img src="./media/readme/package_view_type.gif" alt="groupBySetting" width="1000"/>
+<img src="media/readme/package_view_type.gif" alt="groupBySetting" width="1000"/>
 
 #### Package Details
 
@@ -88,26 +88,26 @@ You can right-click on each detail and copy the value to the clipboard.
 - Last pushed date/time
 
 
-<img src="./media/readme/package_details.gif" alt="packageDetails" width="350"/>
+<img src="media/readme/package_details.gif" alt="packageDetails" width="350"/>
 
 #### Package Context Menus
 
 The right-click menu provides access to the following commands varying depending on whether you have enabled the package groups setting. 
 
-<img src="./media/readme/package_context_menu.gif" alt="contextMenu" width="400"/>
+<img src="media/readme/package_context_menu.gif" alt="contextMenu" width="400"/>
 
 #### Package Inspect
 
 Selecting inspect will return the raw JSON data for the selected item. By default it will send the output to the `Output` window. You can configure for output to be sent to a new text document instead. 
 
-<img src="./media/readme/package_inspect.gif" alt="inspectPackage"/>
+<img src="media/readme/package_inspect.gif" alt="inspectPackage"/>
 
 #### Open Package in Cloudsmith
 
 You can open the package directly in your Cloudsmith Web App.
 
 
-<img src="./media/readme/package_open_browser.gif" alt="openPackage" width="1000"/>
+<img src="media/readme/package_open_browser.gif" alt="openPackage" width="1000"/>
 
 
 ## Limitations & known issues

package.json

@@ -1,7 +1,7 @@
 {
   "name": "cloudsmith-vsc",
   "publisher": "Cloudsmith",
-  "displayName": "Cloudsmith",
+  "displayName": "Cloudsmith VSCode",
   "description": "Access your artifacts from Cloudsmith instance.",
   "version": "1.0.0",
   "license": "SEE LICENSE IN LICENSE",

vsc-extension-quickstart.md

@@ -0,0 +1,42 @@
+# Welcome to your VS Code Extension
+
+## 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`.
+
+## 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.
+
+## 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.
+
+## Explore the API
+
+* 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.
+
+## 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.