DevTools/CodingStandards: Difference between revisions

Jump to navigation Jump to search
Add VS Code config
(added windows path)
(Add VS Code config)
Line 133: Line 133:


You probably need to close and reopen ViM for the changes to take effect. Then, open any file and try to edit it to cause an error, then save it. If all goes well, you will get some distinctive arrows pointing to the error. Hovering with the mouse will produce a sort of tooltip with more information about the error.
You probably need to close and reopen ViM for the changes to take effect. Then, open any file and try to edit it to cause an error, then save it. If all goes well, you will get some distinctive arrows pointing to the error. Hovering with the mouse will produce a sort of tooltip with more information about the error.
=== Running ESLint in Visual Studio Code ===
From the root of the project type:
<code>./mach eslint --setup</code>
Install the [https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint dbaeumer.vscode-eslint] package. Then go to the package settings and set the following option:
<code>"eslint.nodePath": "tools/lint/eslint/node_modules/.bin"</code>
Once done, you should see errors and warnings as shown in the screenshot below.
[[File:vscode-eslint.png|ESLint in VS Code]]


=== Getting Rid of ESLint Errors ===
=== Getting Rid of ESLint Errors ===
Confirmed users
231

edits

Navigation menu