From 61b55f1944ce3e6ec6a1d4073f018ce5de7a4bd5 Mon Sep 17 00:00:00 2001 From: Gama11 Date: Mon, 30 Jan 2017 00:25:45 +0100 Subject: [PATCH] Don't show diagnostics for files in /cases [skip ci] --- .vscode/settings.json | 3 ++- README.md | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index 76d3f9f..1a3fcbb 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -2,5 +2,6 @@ "editor.insertSpaces": true, "haxe.displayConfigurations": [ ["complete.hxml"] - ] + ], + "haxe.diagnosticsPathFilter": "${workspaceRoot}/src" } diff --git a/README.md b/README.md index 22e17cb..3961ae4 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ So when adding a new test, follow these steps: For convenience, there exists a `haxe all.hxml`, which runs both the conversion and the tests. If you have this project open in VSCode, you can just execute the build task (Ctrl+Shift+B) to execute `all.hxml`. -VSCode currently needs to be restarted to pick up changes to grammar files. Hence it is helpful to assign an easily accessible shortcut to the `Reload Window` command, for instance F6. Sublime Text's [PackageDev](https://github.com/SublimeText/PackageDev) extension may offer a better workflow in this regard. +VSCode currently needs to be restarted to pick up changes to grammar files. Hence it is helpful to assign an easily accessible shortcut to the `Reload Window` command, for instance F6. Sublime Text's [PackageDev](https://github.com/SublimeText/PackageDev) extension may offer a better workflow in this regard. The following VSCode extensions are helpful for working on the grammar files: