Hey guys :) I noticed that you currently use a 'lint' name for the script which runs Prettier for code formatting.
I am referencing this part of the code, inside package.json:
While Prettier is excellent for enforcing code formatting rules, it's not designed to catch other types of issues like ESLint does. By using ESLint additionally, you can achieve a more comprehensive approach to code quality and style consistency.
My proposal is to install and configure eslint for this repo and I can assist with setting up the initial configuration if needed.
Thank you for considering this proposal to integrate ESLint into this project. I believe that adopting ESLint will significantly enhance the codebase's quality and maintainability, leading to a more efficient and collaborative development process.
Hey guys :) I noticed that you currently use a 'lint' name for the script which runs Prettier for code formatting.
I am referencing this part of the code, inside package.json:
While Prettier is excellent for enforcing code formatting rules, it's not designed to catch other types of issues like ESLint does. By using ESLint additionally, you can achieve a more comprehensive approach to code quality and style consistency.
My proposal is to install and configure eslint for this repo and I can assist with setting up the initial configuration if needed.
Thank you for considering this proposal to integrate ESLint into this project. I believe that adopting ESLint will significantly enhance the codebase's quality and maintainability, leading to a more efficient and collaborative development process.