Pulling feat/eslint-upgrade into develop#1009
Open
github-actions[bot] wants to merge 17 commits into
Open
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1009 +/- ##
===========================================
- Coverage 92.54% 90.76% -1.79%
===========================================
Files 417 360 -57
Lines 23582 20727 -2855
Branches 1162 941 -221
===========================================
- Hits 21823 18812 -3011
- Misses 1756 1912 +156
Partials 3 3 🚀 New features to boost your workflow:
|
Collaborator
|
Some eslint plugins have not been updated to be compatible with ESLint version 9 use https://eslint.org/blog/2024/05/eslint-compatibility-utilities/ |
This commit introduces a custom ESLint configuration package (`eslint-config-custom-9`) to enforce code style and quality rules across the project. The package includes a rule to enforce the use of semicolons and configures ESLint to apply to all TypeScript files in the `src` directory.
The eslint-plugin-github plugin is added to provide GitHub-specific linting rules. The tsconfig dependency is added to allow the eslint config to use the tsconfig.json file.
…or tsx files Integrates eslint-plugin-github to enforce GitHub-specific linting rules and adds support for linting .tsx files. This ensures code adheres to GitHub's best practices and extends linting to React components.
Adds eslint plugins to improve code quality: - eslint-plugin-prettier: integrates prettier with eslint - eslint-plugin-sonarjs: detects bugs and code smells - eslint-plugin-unicorn: enforces code style and best practices
…slint
This commit introduces several enhancements to the ESLint configuration:
- Integrates `eslint-plugin-sonarjs` to enforce SonarJS coding standards,
improving code quality and maintainability.
- Adds `eslint-plugin-unicorn` with its recommended rules to promote
consistent and modern JavaScript/TypeScript code.
- Configures ESLint to properly lint TypeScript files (`.ts`, `.tsx`) by
specifying the appropriate parser and settings. This includes setting
the import parser and resolver to handle TypeScript-specific syntax and
module resolution.
This commit updates various dependencies in the `yarn.lock` file. The updates include both minor and patch version bumps for packages such as `@eslint/*`, `browserslist`, `core-js-compat`, `eslint-plugin-unicorn`, and many others. The dependency updates are performed to ensure that the project is using the latest versions of its dependencies, which may include bug fixes, performance improvements, and new features. Updating dependencies also helps to maintain compatibility with other packages and tools in the ecosystem.
This commit updates the yarn.lock file to reflect changes in dependencies. The yarn.lock file is updated to ensure that the project uses the correct versions of dependencies.
This commit adds a new file named `eslint8-rules.json` to the repository. This file contains the ESLint configuration rules for the project. It includes various rules for JavaScript, TypeScript, React, accessibility, and other code quality aspects. The rules are configured to enforce code style, prevent errors, and improve the overall maintainability of the codebase. feat: add eslint9-rules.json file with eslint rules This commit introduces a new file, `eslint9-rules.json`, which contains the ESLint rules for the project. The rules are configured to enforce code quality, consistency, and best practices. It also includes configurations for typescript, react, import and unicorn plugins. The file also disables all stylistic rules as prettier is used for formatting.
This commit introduces a new ESLint configuration file specifically tailored for React applications. This configuration includes a set of recommended rules and plugin configurations to enforce code quality, best practices, and consistency in React projects. The configuration includes plugins for React, import statements, JSX accessibility, and React Hooks. It also defines a comprehensive set of rules to catch potential errors, enforce code style, and improve the overall maintainability of React applications.
This commit adds more eslint plugins and configs to the eslint config. The added plugins are: - @eslint/compat - @eslint/eslintrc - eslint-config-airbnb - eslint-config-react-app - eslint-plugin-compat - eslint-plugin-import - eslint-plugin-jsx-a11y - eslint-plugin-react - eslint-plugin-react-hooks These plugins will help us to write more consistent and maintainable code.
Adds more plugins and configs to eslint, including: - eslint-plugin-compat - eslint-plugin-prettier/recommended - reactApp config clone This commit configures eslint with more plugins and configs to improve code quality and consistency. The compat plugin helps ensure that the code is compatible with different browsers. The prettier plugin automatically formats the code. The reactApp config clone provides a good starting point for linting React applications.
…onfigs This commit integrates the typescript eslint configuration and reorders the eslint configurations to ensure proper linting and formatting. The typescript config is now included for better typescript support. The order of configurations has been adjusted to ensure that the most important rules are applied first, and prettier is applied last to avoid conflicts.
Adds a new eslint configuration for typescript files. This configuration includes the typescript eslint plugin and parser, and sets up rules specific to typescript. It also disables some eslint rules that are already handled by the typescript compiler. This change enables eslint to lint typescript files in the project.
The eslint config was not matching the correct name, so it was updated to match the correct name.
This change adds an ESLint configuration file to the dicty-frontpage application. This will help ensure code quality and consistency by enforcing coding standards. The configuration extends a custom ESLint configuration.
Adds declaration files for eslint plugins to prevent typescript errors when importing eslint plugins.
ktun95
force-pushed
the
feat/eslint-upgrade
branch
from
f6c2d73 to
2a99426
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.