Update linting instructions to reference new script name (#320)

This commit is contained in:
Linus Unnebäck 2018-11-07 19:44:38 +00:00 committed by Daniel Wirtz
parent ef3b47d91c
commit 7135af36bd
4 changed files with 4 additions and 3 deletions

View File

@ -42,7 +42,7 @@ Instructions are similar to those for bug reports. Please provide the following
Before submitting your pull request, please make sure that the following conditions are met:
* Your new code **adheres to the code style** through running `npm run lint`.
* Your new code **adheres to the code style** through running `npm run check`.
* Your new code **passes all existing and new tests** through running `npm run test:pr`.
* Your PR **excludes distribution files** in `dist/**`.
* You appended yourself to the **list of contributors** in the [NOTICE](./NOTICE) file.

1
NOTICE
View File

@ -9,6 +9,7 @@ under the licensing terms detailed in LICENSE:
* Norton Wang <me@nortonwang.com>
* Alan Pierce <alangpierce@gmail.com>
* Palmer <pengliao@live.cn>
* Linus Unnebäck <linus@folkdatorn.se>
Portions of this software are derived from third-party works licensed under
the following terms:

View File

@ -93,7 +93,7 @@ $> npm run clean
Linting potential changes:
```
$> npm run lint
$> npm run check
```
Running the [tests](./tests):

View File

@ -29,7 +29,7 @@ Add a script to your `package.json`:
Now, to check your sources, run:
```
$> npm run lint
$> npm run check
```
If you are using [Visual Studio Code](https://code.visualstudio.com/), there's also a [TSLint extension](https://marketplace.visualstudio.com/items?itemName=eg2.tslint) that highlights issues as you type.