@funboxteam/eslint-plugin-no-only-tests - npm Package Compare versions

Comparing version 4.0.0 to 4.0.1

CHANGELOG.md

		# Changelog

		## 4.0.1 (10.06.2021)

		Fixed several security vulnerabilities:

		- [Prototype Pollution](https://github.com/advisories/GHSA-c4w7-xm78-47vh) in [y18n](https://github.com/yargs/y18n). Updated from 3.2.1 to 3.2.2.

		- [Prototype Pollution](https://github.com/advisories/GHSA-p6mc-m468-83gw) and [Command Injection](https://github.com/advisories/GHSA-35jh-r3h4-6jhm) in [lodash](https://github.com/lodash/lodash). Updated from 4.17.15 to 4.17.21.

		- and others.


		## 4.0.0 (23.06.2020)
		@@ -4,0 +15,0 @@

package.json

		{
		"name": "@funboxteam/eslint-plugin-no-only-tests",
		"version": "4.0.0",
		"version": "4.0.1",
		"description": "Disallow the use of describe.only() and it.only()",
		@@ -25,4 +25,4 @@ "keywords": [
		"eslint": "5.16.0",
		"mocha": "8.0.1"
		"mocha": "8.4.0"
		}
		}

README.md

		@@ -13,5 +13,6 @@ # @funboxteam/eslint-plugin-no-only-tests

		However, such filters should not be in the repo when the project is running on CI. So, we add this rule to our ESLint config
		to check the existence of `only` in the tests files. And we run linter using precommit-hook,
		which make it possible to prevent committing when `only` does exist in the code.
		However, such filters should not be in the repo when the project is running on CI.
		So, we add this rule to our [ESLint config](https://github.com/funbox/eslint-config) to check the existence of `only`
		in the tests files. And we run linter using precommit-hook, which make it possible to prevent committing
		when `only` does exist in the code.

		@@ -39,5 +40,5 @@ ## Installation
		{
		"plugins": [
		"@funboxteam/no-only-tests"
		]
		"plugins": [
		"@funboxteam/no-only-tests"
		]
		}
		@@ -51,5 +52,5 @@ ```
		{
		"rules": {
		"@funboxteam/no-only-tests/no-only": 2
		}
		"rules": {
		"@funboxteam/no-only-tests/no-only": 2
		}
		}
		@@ -56,0 +57,0 @@ ```

README.ru.md

		@@ -12,3 +12,4 @@ # @funboxteam/eslint-plugin-no-only-tests

		Однако, на CI нужно запускать все тесты. Потому мы добавляем в линтер правило, которое проверяет,
		Однако, на CI нужно запускать все тесты.
		Потому мы включаем в нашем [ESLint-конфиге](https://github.com/funbox/eslint-config) этот плагин, и он проверяет,
		не используется ли метод `only` в файлах с тестами. А сам линтер запускаем с помощью прекоммит-хука,
		@@ -38,5 +39,5 @@ тем самым блокируя возможность коммита в случае наличия `only` в кодовой базе.
		{
		"plugins": [
		"@funboxteam/no-only-tests"
		]
		"plugins": [
		"@funboxteam/no-only-tests"
		]
		}
		@@ -50,5 +51,5 @@ ```
		{
		"rules": {
		"@funboxteam/no-only-tests/no-only": 2
		}
		"rules": {
		"@funboxteam/no-only-tests/no-only": 2
		}
		}
		@@ -55,0 +56,0 @@ ```

New alerts