chore: remove unused eslint-disable comments after eslint upgrades #861
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.
Description
After recent Dependabot upgrades to
@metamask/eslint-config-jest(14.1.0 → 15.0.0) and@metamask/auto-changelog(5.2.0 → 5.3.0), several eslint-disable comments became unnecessary. This PR removes those unused disable comments to clean up the codebase.The changes include:
@typescript-eslint/naming-conventiondisable comments in global.d.ts filesjest/no-conditional-in-testdisable comments that are no longer needed@typescript-eslint/no-unsafe-enum-comparisondisable comments in switch statementsThese changes were made by running
yarn lint:fixafter the eslint configuration upgrades.Related issues
Fixes: N/A (cleanup after automated dependency upgrades)
Manual testing steps
yarn installyarn lintto verify no linting errorsyarn testto ensure all tests passScreenshots/Recordings
N/A - This is a code cleanup change with no visual impact.
Before
Eslint warnings about unused disable comments
After
Running
yarn lint:fixreturns no eslint warningslint.fix.mov
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Removes obsolete eslint-disable comments (e.g., jest/no-conditional-in-test, @typescript-eslint/no-unsafe-enum-comparison, naming-convention) across test files and d.ts declarations with no functional changes.
eslint-disablecomments across multiple packages/tests.packages/design-system-react-native/global.d.ts,packages/design-system-react/global.d.ts: drop@typescript-eslint/naming-conventiondisables in*.svgmodule declarations.packages/design-system-react/scripts/create-component/create-component.test.ts: removejest/no-conditional-in-testdisables infs.readFilemocks.packages/design-system-react/src/components/Icon/template.test.ts: keep only@typescript-eslint/no-base-to-stringdisable; removejest/no-conditional-in-testfrom comment.packages/design-system-tailwind-preset/src/{colors,index,typography}.test.ts: removejest/no-conditional-in-testdisables from filtering/theme mocks.scripts/create-package/utils.test.ts: removejest/no-conditional-in-testand@typescript-eslint/no-unsafe-enum-comparisondisables in switch cases.scripts/create-package/utils.ts: remove@typescript-eslint/no-unsafe-enum-comparisondisables inprocessTemplateContentswitch.Written by Cursor Bugbot for commit 1c2726d. This will update automatically on new commits. Configure here.