ci: introduce workflow for linter#183
Conversation
feat: Implement linter and prettier
Summary of ChangesHello @guglielmo-san, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request establishes a robust linting workflow for the project by introducing a new ESLint configuration tailored for TypeScript. The setup integrates essential tools for code quality and style consistency, including specific rule adjustments to align with project practices and testing frameworks. This foundational change ensures a higher standard of code maintainability and readability going forward. Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces ESLint to the project, which is a great step for maintaining code quality. The configuration in eslint.config.mjs is a good start, but has a critical issue with how the configuration is exported, which will prevent it from working. I've left comments with suggestions to fix this. I've also pointed out that globally disabling @typescript-eslint/no-explicit-any is not recommended and provided an alternative. The rest of the changes are lint fixes, which look correct and improve the codebase by removing unused code.
Description
This pull request introduces a new ESLint configuration file,
eslint.config.mjsto standardize code quality and style across the project.Here's a summary of the key changes:
Custom Rule Adjustments:
Test File Specific Rules:
Node.js Global Variables: The configuration now includes globals.node to correctly recognize Node.js global variables, preventing false positives for undefined variables in Node.js environments.
The changes in other files in this PR are necessary for the linter checks to pass. They involve mainly the removal of unused parameters.
Re #177 🦕