Adds a note in the Linting section about updating VSCode settings to see "live" linting for TypeScript.
This commit is contained in:
parent
ba6e295e42
commit
95c362805e
|
@ -255,6 +255,17 @@ IntelliJ | Settings » Languages & Frameworks » JavaScript » Code Quality To
|
|||
|
||||
Another tool we use for enforcing consistent coding style is EditorConfig, which can be set up by installing a plugin in your editor that dynamically updates its configuration. Take a look at the [EditorConfig](http://editorconfig.org/#download) site to find a plugin for your editor, and browse our [`.editorconfig`](https://github.com/elastic/kibana/blob/master/.editorconfig) file to see what config rules we set up.
|
||||
|
||||
Note that for VSCode, to enable "live" linting of TypeScript (and other) file types, you will need to modify your local settings, as shown below. The default for the ESLint extension is to only lint JavaScript file types.
|
||||
|
||||
```json
|
||||
"eslint.validate": [
|
||||
"javascript",
|
||||
"javascriptreact",
|
||||
"typescript",
|
||||
"typescriptreact",
|
||||
]
|
||||
```
|
||||
|
||||
### Internationalization
|
||||
|
||||
All user-facing labels and info texts in Kibana should be internationalized. Please take a look at the [readme](packages/kbn-i18n/README.md) and the [guideline](packages/kbn-i18n/GUIDELINE.md) of the i18n package on how to do so.
|
||||
|
|
Loading…
Reference in a new issue