Bump packages to fix linter
This commit is contained in:
parent
ed9506bbaf
commit
0a11e3fdd9
6063 changed files with 378752 additions and 306784 deletions
73
node_modules/eslint-plugin-no-only-tests/README.md
generated
vendored
73
node_modules/eslint-plugin-no-only-tests/README.md
generated
vendored
|
|
@ -2,22 +2,22 @@
|
|||
|
||||
[](https://www.npmjs.com/package/eslint-plugin-no-only-tests) [](https://npmcharts.com/compare/eslint-plugin-no-only-tests?minimal=true) [](https://github.com/levibuzolic/eslint-plugin-no-only-tests/actions?query=workflow%3ATests)
|
||||
|
||||
ESLint rule for `.only` tests in [mocha](https://mochajs.org/) and other JS testing libraries.
|
||||
ESLint rule for `.only` tests in [mocha](https://mochajs.org/), [jest](https://jestjs.io/), [jasmine](https://jasmine.github.io/), [Mocha Cakes 2](https://github.com/iensu/mocha-cakes-2) and other JS testing libraries.
|
||||
|
||||
Currently matches the following test blocks by default: `describe`, `it`, `context`, `tape`, `test`, `fixture`, `serial`.
|
||||
By default the following test blocks are matched by default: `describe`, `it`, `context`, `tape`, `test`, `fixture`, `serial`.
|
||||
|
||||
Designed to prevent you from committing `.only` tests to CI, disabling tests for your whole team.
|
||||
Designed to prevent you from committing focused (`.only`) tests to CI, which may prevent your entire test suite from running.
|
||||
|
||||
As of v2.3 you can now override the test blocks and focus functions.
|
||||
If the testing framework you use doesn't use `.only` to focus tests, you can override the matchers with [options](#options).
|
||||
|
||||
## Installation
|
||||
|
||||
First you'll need to install [ESLint](http://eslint.org) then the plugin:
|
||||
[Install ESLint](https://eslint.org/docs/user-guide/getting-started) if you haven't done so already, then install `eslint-plugin-no-only-tests`:
|
||||
|
||||
```bash
|
||||
npm install --save-dev eslint eslint-plugin-no-only-tests
|
||||
npm install --save-dev eslint-plugin-no-only-tests
|
||||
# or
|
||||
yarn add --dev eslint eslint-plugin-no-only-tests
|
||||
yarn add --dev eslint-plugin-no-only-tests
|
||||
```
|
||||
|
||||
> **Note:** If you installed ESLint globally (using the `-g` flag) then you must also install `eslint-plugin-no-only-tests` globally.
|
||||
|
|
@ -27,42 +27,39 @@ yarn add --dev eslint eslint-plugin-no-only-tests
|
|||
Add `no-only-tests` to the plugins section of your `.eslintrc` configuration file. You can omit the `eslint-plugin-` prefix:
|
||||
|
||||
```json
|
||||
{
|
||||
"plugins": [
|
||||
"no-only-tests"
|
||||
"plugins": [
|
||||
"no-only-tests"
|
||||
]
|
||||
```
|
||||
|
||||
Then add the rule to the rules section of your `.eslintrc`:
|
||||
|
||||
```json
|
||||
"rules": {
|
||||
"no-only-tests/no-only-tests": "error"
|
||||
}
|
||||
```
|
||||
|
||||
If you use a testing framework that uses a test block name that isn't present in the [defaults](#options), or a different way of focusing test (something other than `.only`) you can specify an array of blocks and focus methods to match in the options.
|
||||
|
||||
```json
|
||||
"rules": {
|
||||
"no-only-tests/no-only-tests": [
|
||||
"error", {
|
||||
"block": ["test", "it", "assert"],
|
||||
"focus": ["only", "focus"]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Then configure the rules you want to use under the rules section.
|
||||
|
||||
```json
|
||||
{
|
||||
"rules": {
|
||||
"no-only-tests/no-only-tests": "error"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
If you use a testing framework that uses an unsupported block name, or a different way of focusing test (something other than `.only`) you can specify an array of blocks and focus methods to match in the options.
|
||||
|
||||
```json
|
||||
{
|
||||
"rules": {
|
||||
"no-only-tests/no-only-tests": ["error", {"block": ["test", "it", "assert"], "focus": ["only", "focus"]}]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
The above example will catch any uses of `test.only`, `test.focus`, `it.only`, `it.focus`, `assert.only` and `assert.focus`.
|
||||
|
||||
This rule supports autofixing only when the `fix` option is set to `true` to avoid changing runtime code unintentionally when configured in an editor.
|
||||
This rule supports opt-in autofixing when the `fix` option is set to `true` to avoid changing runtime code unintentionally when configured in an editor.
|
||||
|
||||
```json
|
||||
{
|
||||
"rules": {
|
||||
"no-only-tests/no-only-tests": ["error", {"fix": true}]
|
||||
}
|
||||
"rules": {
|
||||
"no-only-tests/no-only-tests": ["error", {"fix": true}]
|
||||
}
|
||||
```
|
||||
|
||||
|
|
@ -70,6 +67,6 @@ This rule supports autofixing only when the `fix` option is set to `true` to avo
|
|||
|
||||
Option | Type | Description
|
||||
---|---|---
|
||||
`block` | `Array<string>` | Specify the block names that your testing framework uses. Defaults to `["describe", "it", "context", "test", "tape", "fixture", "serial"]`
|
||||
`focus` | `Array<string>` | Specify the focus scope that your testing framework uses. Defaults to `["only"]`
|
||||
`fix` | `boolean` | Enable this rule to auto-fix violations, useful for a pre-commit hook, not recommended for users with auto-fixing enabled in their editor. Defaults to `false`
|
||||
`block` | `string[]` | Specify the block names that your testing framework uses. Add a `*` to the end of any string to enable prefix matching (ie. `test*` will match `testExample.only`)<br>Defaults to `["describe", "it", "context", "test", "tape", "fixture", "serial", "Feature", "Scenario", "Given", "And", "When", "Then"]`
|
||||
`focus` | `string[]` | Specify the focus scope that your testing framework uses.<br>Defaults to `["only"]`
|
||||
`fix` | `boolean` | Enable this rule to auto-fix violations, useful for a pre-commit hook, not recommended for users with auto-fixing enabled in their editor.<br>Defaults to `false`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue