Skip to content

Commit

Permalink
Don't show diagnostics for files in /cases
Browse files Browse the repository at this point in the history
[skip ci]
  • Loading branch information
Gama11 committed Jan 29, 2017
1 parent 6d2453e commit 61b55f1
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
3 changes: 2 additions & 1 deletion .vscode/settings.json
Expand Up @@ -2,5 +2,6 @@
"editor.insertSpaces": true,
"haxe.displayConfigurations": [
["complete.hxml"]
]
],
"haxe.diagnosticsPathFilter": "${workspaceRoot}/src"
}
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -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 (<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>B</kbd>) 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 <kbb>F6</kbd>. 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 <kbd>F6</kbd>. 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:

Expand Down

0 comments on commit 61b55f1

Please sign in to comment.