BREAKING CHANGE: migrating rules to eslint9 #100
Closed
+12,164
−9,658
Conversation
This file contains 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
…ds on eslint-plugin-react
|
Why does it need to be a breaking change? |
|
@ljharb It hopefully does not have to be. Currently to migrate to eslint 9 I need to deprecate/exclue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
also eslint-plugin-airbnb migration to v9 is in progress airbnb/javascript#2961 so the cod is not linted properly.
So all and all we are quite early to the party.
Update: I don't think we can release until the rest of the deps release v9 support. So this branch will stay as a POC. I don't want to force override peer dep requirements, so this branch will stay as a POC and will wait for the rest of the eco system to catch up.