-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(lint): unite eslint rules #2691
Conversation
Code Climate has analyzed commit f05e7ca and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 65.3% (0.0% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase the changes from the main-beta
branch or branch mentioned in the ticket.
The code here looks to be outdated and not compatible with ESLint 9
1dd5f6e
to
08e9caa
Compare
08e9caa
to
0d3fb61
Compare
🎉 This PR is included in version 5.0.0-beta.37 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Closes #2689
Even though original thought was to have only a single rule for each version, but it turned out to be incorrect from user's perspective. Pretty much we have 3 different rule cases:
If we combine all of them into one, there might be a case where the user has only path error. Since we declare our new combined rule as auto fixable, it will misinform user about us automatically fixing his problem. Which is false information.
That's why it was decided to only combine alias rules into one + refactor other rules to accept array of rule cases