Use ESLint Stylistic without hard wrapping - #6
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
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 is an alternative to #5. It enforces the existing preferences for tabs, single quotes, semicolons, spacing, and trailing commas without deciding when arrays, calls, or expressions should wrap.
Churn
The JavaScript changes are almost entirely removal of trailing whitespace, plus two import-spacing fixes and one quote normalization. Most of the raw diff size comes from adding ESLint dependencies to
package-lock.json.Validation
npm cinpm run format:checknpm test(858 tests)