wiki.techinc.nl/tests/qunit/.eslintrc.json

{
	"root": true,
	"extends": [
		"wikimedia/client-common",
		"wikimedia/language/es2020",
		"wikimedia/jquery",
		"wikimedia/mediawiki",
		"wikimedia/qunit"
	],
	"globals": {
		"sinon": "readonly"
	},
	"rules": {
		"compat/compat": [ "error", "last 2 chrome versions, last 2 firefox versions" ],
		"max-len": "off",
		"no-jquery/no-global-selector": "off",
		"no-jquery/no-parse-html-literal": "off",
		"no-shadow": [ "error", { "allow": [ "hooks" ] } ],
		"qunit/resolve-async": "off"
	}
}
qunit: Make eslint config pass on qunit test files Follows-up c0fb8a8836, I890e6e49b. * Disable 'qunit' env in general source code. And re-declare locally in the few src files that use it properly. * Create separate eslint config for tests/qunit with various rules disabled (e.g. valid-jsdoc and es3-keywords). Change-Id: I37ccec2019de55edfee92697eb80478df7cb6220 2017-02-22 18:46:19 +00:00			`{`
eslint: Only apply client rules to client files Change-Id: I757b9616ce69b6020e9f0e556e006d39de59eb01 2022-02-07 16:09:22 +00:00			`"root": true,`
build: Introduce eslint-plugin-qunit and enforce Change-Id: Iefe06cc865c458000ca5350c2d9205f5b768bac8 2018-06-05 20:58:25 +00:00			`"extends": [`
tests: Configure ESLint to permit ES2022 syntax in test suites Analogous to what the 'compat/compat' rule indicates already, and the fact that CI, fresh-node, and local dev generally involves recent versions of Firefox, Chromium-based browsers, or Safari. This patch is a minimal first step that only loosens the linter, and auto-fixing only unusual cases where a new rule specifically warned against existing code. Change-Id: Ic64f650bd64669c57b884de3f75b23f3549b0c9f 2023-04-15 23:32:52 +00:00			`"wikimedia/client-common",`
			`"wikimedia/language/es2020",`
			`"wikimedia/jquery",`
			`"wikimedia/mediawiki",`
eslint: Only apply client rules to client files Change-Id: I757b9616ce69b6020e9f0e556e006d39de59eb01 2022-02-07 16:09:22 +00:00			`"wikimedia/qunit"`
build: Introduce eslint-plugin-qunit and enforce Change-Id: Iefe06cc865c458000ca5350c2d9205f5b768bac8 2018-06-05 20:58:25 +00:00			`],`
qunit: Make eslint config pass on qunit test files Follows-up c0fb8a8836, I890e6e49b. * Disable 'qunit' env in general source code. And re-declare locally in the few src files that use it properly. * Create separate eslint config for tests/qunit with various rules disabled (e.g. valid-jsdoc and es3-keywords). Change-Id: I37ccec2019de55edfee92697eb80478df7cb6220 2017-02-22 18:46:19 +00:00			`"globals": {`
eslint: Use correct global values, and use jquery rules in selenium tests Change-Id: Ie9fe9fc872db2e4dd0266395f112cc18d3deb807 2019-10-04 14:53:11 +00:00			`"sinon": "readonly"`
qunit: Make eslint config pass on qunit test files Follows-up c0fb8a8836, I890e6e49b. * Disable 'qunit' env in general source code. And re-declare locally in the few src files that use it properly. * Create separate eslint config for tests/qunit with various rules disabled (e.g. valid-jsdoc and es3-keywords). Change-Id: I37ccec2019de55edfee92697eb80478df7cb6220 2017-02-22 18:46:19 +00:00			`},`
			`"rules": {`
eslint: Only apply client rules to client files Change-Id: I757b9616ce69b6020e9f0e556e006d39de59eb01 2022-02-07 16:09:22 +00:00			`"compat/compat": [ "error", "last 2 chrome versions, last 2 firefox versions" ],`
tests: Configure ESLint to permit ES2022 syntax in test suites Analogous to what the 'compat/compat' rule indicates already, and the fact that CI, fresh-node, and local dev generally involves recent versions of Firefox, Chromium-based browsers, or Safari. This patch is a minimal first step that only loosens the linter, and auto-fixing only unusual cases where a new rule specifically warned against existing code. Change-Id: Ic64f650bd64669c57b884de3f75b23f3549b0c9f 2023-04-15 23:32:52 +00:00			`"max-len": "off",`
			`"no-jquery/no-global-selector": "off",`
eslint: Only apply client rules to client files Change-Id: I757b9616ce69b6020e9f0e556e006d39de59eb01 2022-02-07 16:09:22 +00:00			`"no-jquery/no-parse-html-literal": "off",`
mediawiki.user: Adopt modern syntax, use nested scope for clientPrefs In prep of the next change, and to keep the setup/teardown logic separated from other tests. Change-Id: I821f8b7321b295f5444a9aef1ecd7d17e0d267d0 2023-10-31 08:53:18 +00:00			`"no-shadow": [ "error", { "allow": [ "hooks" ] } ],`
eslint: Only apply client rules to client files Change-Id: I757b9616ce69b6020e9f0e556e006d39de59eb01 2022-02-07 16:09:22 +00:00			`"qunit/resolve-async": "off"`
build: Update eslint-config-wikimedia to 0.7.2 Change-Id: Ibdf9cc013e1265ef461169ec2227652eaf917900 2018-08-14 18:24:51 +00:00			`}`
qunit: Make eslint config pass on qunit test files Follows-up c0fb8a8836, I890e6e49b. * Disable 'qunit' env in general source code. And re-declare locally in the few src files that use it properly. * Create separate eslint config for tests/qunit with various rules disabled (e.g. valid-jsdoc and es3-keywords). Change-Id: I37ccec2019de55edfee92697eb80478df7cb6220 2017-02-22 18:46:19 +00:00			`}`