Improve operator-linebreak formatting rules #231
Merged
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
- Add overrides for assignment operators (=, +=, -=, *=, /=) to appear after the operator - Bump eslint-config-internal to v1.3.1 - Bump eslint-config-react-internal to v0.1.3 with updated dependency 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Andr1yK
approved these changes
Jul 28, 2025
marina-tilniak
approved these changes
Jul 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
• Enhanced
operator-linebreakESLint rule with overrides for assignment operators• Assignment operators (=, +=, -=, *=, /=) now appear after the variable for better readability
• Updated package versions for both internal ESLint configs
Test plan
🤖 Generated with Claude Code