Fix: Integrate ESLint into build pipeline (OWASP#2647)#2828
Fix: Integrate ESLint into build pipeline (OWASP#2647)#2828Adarshkumar0509 wants to merge 55 commits intoOWASP:masterfrom
Conversation
- Added lint script to package.json - Wired lint into the build pipeline - Fixed ~300 lint errors across src files - Used Claude (Anthropic) to assist with fixes Pre-existing coverage threshold issue (93.28% vs 95%) exists on master and is not introduced by this PR.
dc1e6d3 to
e116285
Compare
|
hello @sydseter sir can you take a look at this whenever u have time or suggest me something in this ? |
|
@sydseter sir, can you review this . |
|
@Adarshkumar0509 Sorry, I didn’t make it and I see now there are conflicts again. |
|
hii @sydseter sir i think i have resolved the conflicts , whenever you have time please take a look. |
This reverts commit 0937488.
|
@Adarshkumar0509 Disable for now. |
|
hii, @sydseter it now passing including build-website and smoke tests. its really helpful if you review this . |
|
I am getting 21 404 issues when running the build: [500] GET /edition/webapp/VE4/3.0/en |
|
I am also see some of the same issues I reported earlier: E.g: I get 404 when navigating to http://localhost:3000/taxonomy/cheat-sheets-asvs-4.0.3/#V5.2-Sanitization-and-Sandboxing-Requirements You can reproduce it by choosing the OWASP Cheat Sheets mapping from here: http://localhost:3000/edition/webapp/VEK/2.2/en#card |
|
Ok sir I will be fixing this just started working on it |
|
hii @sydseter , all things are addressed and also verified locally its working can you take a look at this ?please let me no if any changes are req because its important |
|
hii @sydseter whenever you have time please take a look. |
…pecMapTable lint errors
|
The corrupted characters were caused by encoding issues and have all been fixed. Please review when you have time. |
|
hii @sydseter, i have addressed all the things and fixed them all and verified locally as well please take a look on this. |



Description
Integrates ESLint into the build pipeline as part of #2647.
Builds on #2675 which added the eslint-config-love configuration.
ESLint Integration (primary scope)
-Integrated eslint-config-love as replacement for ts-standard (incompatible with TypeScript 5.9.3)
-Added ESLint to the build pipeline via pnpm run lint in the build script
-Configured eslint.config.js with @typescript-eslint/no-unused-vars rules with _ prefix pattern
-Added coverage/ to ESLint ignore list to prevent linting auto-generated files
Bug fixes made during integration
-Fixed spacer.svelte CSS property was incorrectly renamed to _height (invalid CSS). Fixed by properly using the height prop via inline style.
-Removed dead code in creController.ts — if (!cre) block was unreachable due to || [] fallback
Test coverage improvements
-TypeScript/Website coverage: 93.28% → 95.45% (now passing) Added missing branch tests for mappingController.ts, creController.ts, and mapping API server
-Elixir/COPI coverage: 92.6% → 93.2% (pre-existing failure, still below 95% threshold)
fixed issue:#2647
AI Tool Disclosure
-AI Tools: Chatgpt
-LLMs and versions: Chatgpt free version
-Prompts: Assisted with identifying lint errors, fixing TypeScript/Svelte ,how to fix this error what is the easiest way to fix as i am doing manually.give some examples and help me in cleanup.
-lint issues, and structuring the PR description.
Affirmation