Enable ESLint Rule for Unused Variables to Improve Code Quality

[lamcodeofpwnosec]

Description of Changes

This pull request enhances code quality by enabling the @typescript-eslint/no-unused-vars rule in the .eslintrc.js configuration file. The rule was previously disabled, which allowed unused variables to remain undetected in the codebase.

Main Changes

1. Enabled @typescript-eslint/no-unused-vars Rule
   • Change: The rule has been updated from 'off' to 'warn'.
   • Purpose: To warn developers about unused variables, helping maintain clean and efficient code.

Reason for Changes

• Activating this rule will assist in identifying and removing variables that are declared but never used, which can:
  • Improve readability and maintainability of the code.
  • Prevent potential bugs or confusion caused by leftover, unused variables.
• This change allows developers to gradually address these warnings without halting the development process, as the rule is set to 'warn' rather than 'error'.

Detailed Changes

• Before: '@typescript-eslint/no-unused-vars': 'off'
• After: '@typescript-eslint/no-unused-vars': 'warn'

The goal is to maintain a cleaner codebase and ensure that all declared variables are actively used. Feel free to review and share any feedback or suggestions for further improvements.

---

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[cb-jake]

Hello @lamcodeofpwnosec thanks for the PR. We're currently debating migrating the repo to biome for formatting and linting. Going to close this as it wont be relevant when we make the switch. Thanks again.