chore(eslint): update to typescript-eslint v8 recommendations#13965
Closed
rubixvi wants to merge 2 commits intopayloadcms:mainfrom
Closed
chore(eslint): update to typescript-eslint v8 recommendations#13965rubixvi wants to merge 2 commits intopayloadcms:mainfrom
rubixvi wants to merge 2 commits intopayloadcms:mainfrom
Conversation
- Replace manual indexing of `recommendedTypeChecked[0-2]` with direct spread of `recommendedTypeChecked` - Ensure compatibility with new flat config array shape introduced in @typescript-eslint v8 - Simplify config merging for TypeScript and React rules
rubixvi
changed the title
Contributor
Author
|
Stale |
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.
What?
This PR updates our ESLint configuration to align with the new recommendations from
@typescript-eslintv8. It removes legacy array indexing and ensures future compatibility.Why?
How?