1.2.2

celian-rib · Jan 22, 2022 · 3c982ad · 3c982ad
1 parent 549b7c7
commit 3c982ad
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 9 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,9 @@
 # W3C Web validator - Change Log
 
+## [1.2.2]
+
+- Better error messaging while W3C validation service is unavailable [#21](https://github.com/celian-rib/vscode-webvalidation-extension/issues/21)
+
 ## [1.2.1]
 
 - Validating on save is no more enabled by default.

diff --git a/package.json b/package.json
@@ -3,7 +3,7 @@
 	"displayName": "W3C Web Validator",
 	"description": "Check the validity of your HTML/CSS files in one click",
 	"publisher": "CelianRiboulet",
-	"version": "1.2.1",
+	"version": "1.2.2",
 	"icon": "images/webvalidator.png",
 	"engines": {
 		"vscode": "^1.52.0"

diff --git a/vsc-extension-quickstart.md → vsc-extension-guide.md b/vsc-extension-quickstart.md → vsc-extension-guide.md
@@ -1,4 +1,4 @@
-# Welcome to your VS Code Extension
+# VS Code Extension guide
 
 ## What's in the folder
 
@@ -18,7 +18,7 @@
 
 ## Make changes
 
-* You can relaunch the extension from the debug toolbar after changing code in `extension.js`.
+* You can relaunch the extension from the debug toolbar after changing code in `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
@@ -30,15 +30,11 @@
 * Open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Extension Tests`.
 * Press `F5` to run the tests in a new window with your extension loaded.
 * See the output of the test result in the debug console.
-* Make changes to `src/test/suite/extension.test.js` or create new test files inside the `test/suite` folder.
+* Make changes to `src/test/suite/extension.test.ts` or create new test files inside the `test/suite` 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
 
- * [Publish your extension](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) on the VSCode extension marketplace.
- * Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).
-
-### Create new release :
+## Create new release :
 
 - Update dependencies ```npm i```
 - Update ./CHANGELOG.md