mediawiki-extensions-Revisi.../.eslintrc.json

{
	"root": true,
	"env": {
		"commonjs": true
	},
	"extends": [
		"wikimedia/client",
		"wikimedia/jquery",
		"wikimedia/mediawiki"
	],
	"globals": {
		"OO": false
	},
	"rules": {
		"max-len": "off",
		"no-jquery/no-global-selector": "off",
		"no-jquery/no-class-state": "off"
	}
}
Add eslint, to be used instead of jscs and/or jshint First I jumped on replacing both jscs and jshint with eslint but it might be premature decision. Although linting with eslint is possible (like in there is wikimedia config for eslint) it is still not clear should it But in case the change happens we will be ready. Apart from config stuff this changes few bits spotted by eslint: improves some indentation, removes weird spaces, completes some doc blocks, changes IIFE forms in tests. These changes do not seem controversial. Change-Id: I9f8bf0f5745da8e662685f4cd879ea4baa609c01 2016-09-01 11:17:47 +00:00			`{`
build: Set "root": true, in .eslintrc.json This ensures that each repository's "npm test" command is fully independent of wherever it might be in the filesystem. Bug: T206485 Change-Id: I5de716c50becf448bf7a1dc4f4fcbf322e47b11c 2018-12-18 02:58:01 +00:00			`"root": true,`
ESLint config for CommonJS module syntax Changes the eslint rules to support "require", "module.exports", and relaxes the top-level lexical scope for each file. FIXME: This allows a combination of CommonJS code, which becomes unsafe global code scope if used in a "scripts" module. What's the correct order of migration steps? Change-Id: I2f80732942a602c0fcff5c0dad1e2afc2640651e 2020-03-29 19:28:15 +00:00			`"env": {`
			`"commonjs": true`
			`},`
build: Update devDependencies Change-Id: Ic278699f631ddc08243ceb68678c0715a19c4304 2018-12-04 23:05:18 +00:00			`"extends": [`
			`"wikimedia/client",`
build: Update linters Change-Id: Ia316dd09b6d6b7452610ff2b8816a146a3bb48a4 2019-12-11 13:42:51 +00:00			`"wikimedia/jquery",`
			`"wikimedia/mediawiki"`
build: Update devDependencies Change-Id: Ic278699f631ddc08243ceb68678c0715a19c4304 2018-12-04 23:05:18 +00:00			`],`
Add eslint, to be used instead of jscs and/or jshint First I jumped on replacing both jscs and jshint with eslint but it might be premature decision. Although linting with eslint is possible (like in there is wikimedia config for eslint) it is still not clear should it But in case the change happens we will be ready. Apart from config stuff this changes few bits spotted by eslint: improves some indentation, removes weird spaces, completes some doc blocks, changes IIFE forms in tests. These changes do not seem controversial. Change-Id: I9f8bf0f5745da8e662685f4cd879ea4baa609c01 2016-09-01 11:17:47 +00:00			`"globals": {`
			`"OO": false`
eslint: Remove old jshint/jscs refs, fix exceptions Change-Id: I56b9f037405d0f93f82dc81dad1cc1b111be338e 2016-11-19 13:37:20 +00:00			`},`
			`"rules": {`
build: Update eslint-config-wikimedia to 0.10.1 Change-Id: I8aeddc384d25318e8618bb617884205f1c0c1f00 2019-02-10 16:54:28 +00:00			`"max-len": "off",`
build: Update dependencies and make them pass Change-Id: Ia7764d44d7fbc8bf5c03e80887b58031a0de5d86 2019-10-23 15:46:39 +00:00			`"no-jquery/no-global-selector": "off",`
			`"no-jquery/no-class-state": "off"`
Add eslint, to be used instead of jscs and/or jshint First I jumped on replacing both jscs and jshint with eslint but it might be premature decision. Although linting with eslint is possible (like in there is wikimedia config for eslint) it is still not clear should it But in case the change happens we will be ready. Apart from config stuff this changes few bits spotted by eslint: improves some indentation, removes weird spaces, completes some doc blocks, changes IIFE forms in tests. These changes do not seem controversial. Change-Id: I9f8bf0f5745da8e662685f4cd879ea4baa609c01 2016-09-01 11:17:47 +00:00			`}`
			`}`