Feature : Refine Linting and Formatting Configuration

[TanmayDhobale]

Updated ESLint and Prettier configs for better code consistency. Includes refined rules and pre-commit hook adjustments to automatically fix format and lint issues, making code contributions smoother.

Changes

• Updated .eslintrc with additional rules for TypeScript, improving code quality and consistency.
• Modified the .prettierrc file to refine formatting rules, ensuring that automatic code formatting aligns with our project's standards.
• Enhanced the pre-commit hooks in .husky/pre-commit to run both formatting and linting fixes automatically, reducing the likelihood of committing code that doesn't meet our guidelines.

Impact

• Contributors will experience fewer discrepancies when pushing code, as the pre-commit hooks now more thoroughly ensure code adheres to our standards.
• These updates aim to streamline the development workflow by reducing manual linting and formatting interventions required from contributors.
• By enforcing a consistent coding style, we improve the readability and maintainability of our codebase.

Testing

• Introduced intentional linting/formatting violations to verify that the pre-commit hooks automatically correct them or block the commit when auto-fixes are not possible.
• Confirmed that the updated configurations do not conflict with our current codebase by successfully committing changes after the updates.

Please review the changes and provide any feedback you might have! fixed #201

[aryanprince]

@TanmayDhobale I also created a similar PR (#244) although I believe it solves a different problem at the moment. Your PR is valuable in that it includes improved formating, linting, and Husky pre-commit configs.

But this PR still has issues with ESLint overwriting rules from Prettier when I tested this PR locally.

Could you also verify by trying format:fix and then lint:fix to see if ESLint is overriding any Prettier changes? See videos here (the 'before changes' one) to see what I'm specifically talking about.

I think best case would be to first merge #244 to fix conflicting style rules, and then bring over all of your additions to linting, formatting, and Husky.

PS: Also, I think it's best if you exclude applying the actual linting/formatting changes to files - and include them in a separate PR. As this PR currently has a lot of file changes irrelevant to the PR topic.

[TanmayDhobale]

@aryanprince yea sure , i am closing this pr now thanks