Change Details

As a developer working on Wikibase, I want to be able to fix linting problems in my code automatically (Similar to WikibaseLexeme) In order to save time and unnecessary CI failures. Wikibase does not have a 'fix' eslint task which means a lot of linting problems need to be fixed manually. **Open questions:** Is it possible to have this as a precommit hook only in cases where .js files are committed?

**Motivation** As a developer working on Wikibase, I want to be able to fix javascript formatting issues in my code automatically in order to save time and unnecessary CI failures. **Suggested Solution** Using eslint's [[ https://eslint.org/docs/user-guide/command-line-interface#fixing-problems, | fix feature ]], introduce a new grunt task `fix-js` to run `eslint --fix` on javascript files. For reference, WikibaseLexeme has a similar grunt task `fix`.. Check their [[ https://github.com/wikimedia/mediawiki-extensions-WikibaseLexeme/blob/wmf/1.34.0-wmf.14/Gruntfile.js | Grunfile ]]

**Motivation** As a developer working on Wikibase, I want to be able to fix linjavascript formatting problemsissues in my code automatically (Similar to WikibaseLexeme) Inin order to save time and unnecessary CI failures. Wikibase does not have a 'fix' eslint task which means a lot of linting problems need to be fixed manually. **Open ques**Suggested Solutions:**** Is it possible to have this as a precommit hook only in cases where .js files are committed?Using eslint's [[ https://eslint.org/docs/user-guide/command-line-interface#fixing-problems, | fix feature ]], introduce a new grunt task `fix-js` to run `eslint --fix` on javascript files. For reference, WikibaseLexeme has a similar grunt task `fix`.. Check their [[ https://github.com/wikimedia/mediawiki-extensions-WikibaseLexeme/blob/wmf/1.34.0-wmf.14/Gruntfile.js | Grunfile ]]