chore: add max-len rule to eslint config #6269
Open
Conversation
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
|
we have already an open PR for it: would you mind help to finalize that one instead? |
|
Thank you for pointing it out! I’ll check #6221 and see if I can help finalize it. |
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.
Summary
This PR adds the missing
max-lenESLint rule as part of issue #6029.✅ Changes made:
'max-len': ['error', { code: 100 }]to enforce line length consistency.The
'comma-dangle'rule already existed, so this completes the remaining part.Let me know if anything needs adjustments!
— Riya 🌸
Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct