Replace deprecated rules and remove fix cycles #478
Merged
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.
Summary
This pull request updates the ESLint configuration files for both JavaScript and TypeScript, focusing on aligning rules with the latest stylistic plugin conventions, simplifying overrides, and disabling or modifying certain rules for better compatibility and maintainability. The most important changes are grouped below.
Stylistic Rules Migration and Consistency:
@stylisticequivalents, includingcomma-dangle,function-call-spacing,jsx-quotes,max-len,max-statements-per-line,no-mixed-operators,no-mixed-spaces-and-tabs, andno-tabsinsrc/configs/javascript.tsfor improved consistency and future compatibility. [1] [2] [3] [4] [5] [6] [7] [8]@stylistic/comma-danglerule configuration to a single string option.@stylistic/quote-propsto quote numbers as property names as was previously achieved with the deprecatedquote-props.Rule Removal and Cleanup:
no-native-reassign,no-return-await,no-negated-in-lhs,valid-jsdoc,require-jsdoc, and various Node-specific rules. [1] [2] [3] [4] [5] [6] [7]no-new-objectfor test files in both JavaScript and TypeScript configs, as the rule is no longer present in the base config. [1] [2]@typescript-eslint/no-empty-interfacerule from the TypeScript config as that prevented use of APIs relying on interface extensions.TypeScript Rule Adjustments:
@typescript-eslintrules related to unsafe operations and template expressions to prevent conflicts and allow for more flexible usage ofanytypes where appropriate. Also disabled@typescript-eslint/no-misused-promisesdue to issues with overloaded functions.General Configuration Improvements: