Ensure eslint is properly configured for all packages (0xsequence#971)#303
Ensure eslint is properly configured for all packages (0xsequence#971)#303Dargon789 merged 3 commits intoDargon789:masterfrom
Conversation
* Updating happy-dom, vitest, prettier, and syncpack dev dependencies * Updating turbo repo * Updating lefthook * Updating rimraf * Updating @types/node * Updating dotenv * Updating nodemon and esbuild for primitives-cli
…ages/indexer (#969) * Move indexer clients to packages/services/indexer and remove old packages/indexer * Disable noUncheckedIndexedAccess for indexer package
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
|
|
@corbanbrook is attempting to deploy a commit to the Foundry development Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Sorry @Dargon789, your pull request is larger than the review limit of 150000 diff characters
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Summary of ChangesHello @Dargon789, 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 significantly refines the development environment by standardizing ESLint configurations across all packages, ensuring consistent code quality and maintainability. It also brings various development dependencies up-to-date, enhancing overall project stability and leveraging newer tooling capabilities. Furthermore, several code generation artifacts were updated, and minor type safety and module import adjustments were made to align with modern TypeScript practices. Highlights
Changelog
Ignored Files
Activity
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 is a significant step towards improving code quality and consistency by setting up ESLint across multiple packages. The changes include adding ESLint configurations, updating package scripts to include linting, and fixing a large number of linting errors. The introduction of linting in the pre-commit hook is a great practice. The code refactoring to improve type safety by replacing any with more specific types and using modern JavaScript features is commendable. I've identified a few areas for improvement, mainly concerning the new ESLint configurations and a minor bug in a test. Overall, this is a very positive and impactful change.
No description provided.