9 Commits

Author	SHA1	Message	Date
James Brunton	1c8e1da11d	Merge branch 'V2' into V2-eslint-ban-ts-comment	2025-09-04 16:13:31 +01:00
James Brunton	94e8f603ff	Enable ESLint no-unused-expressions rule (#4363) ... # Description of Changes Enable ESLint [no-unused-expressions rule](https://typescript-eslint.io/rules/no-unused-expressions/)	2025-09-04 15:12:38 +00:00
James Brunton	74609e54fe	Enable ESLint prefer-const rule (#4349) ... # Description of Changes Enable ESLint [prefer-const rule](https://eslint.org/docs/latest/rules/prefer-const)	2025-09-04 15:09:29 +00:00
James Brunton	003285506f	Enable ESLint no-useless-escape rule (#4344) ... # Description of Changes Enable ESLint [no-useless-escape rule](https://eslint.org/docs/latest/rules/no-useless-escape)	2025-09-04 15:04:49 +00:00
James Brunton	6d3b08d9b6	Enable ESLint no-empty rule (#4342) ... # Description of Changes Enable ESLint [no-empty rule](https://eslint.org/docs/latest/rules/no-empty)	2025-09-04 15:59:31 +01:00
James Brunton	295e682e03	Add linting to frontend (#4341) ... # Description of Changes There's no current linter running over our TypeScript code, which means we've got a bunch of dead code and other code smells around with nothing notifying us. This PR adds ESLint with the typescript-eslint plugin and enables the recommended settings as a starting point for us. I've disabled all of the failing rules for the scope of this PR, just to get linting running without causing a massive diff. I'll follow up with future PRs that enable the failing rules one by one. Also updates our version of TypeScript, which introduces a new type error in the code (which I've had to fix)	2025-09-04 14:08:28 +01:00
James Brunton	72668b2e88	Enable ESLint rule ban-ts-comment	2025-09-02 17:58:02 +01:00
James Brunton	65e331ae26	Tidy keys	2025-09-02 17:37:15 +01:00
James Brunton	3d9fd21b1d	Add eslint config	2025-09-02 16:17:01 +01:00