Skip to content

[New] jsx-props-no-multi-spaces: Add automatic fix for no line gap between props #3930

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

Merged

Conversation

justisb
Copy link
Contributor

@justisb justisb commented Jun 3, 2025

Extends automatic fix support to cover the "no line gap" half of the jsx-props-no-multi-spaces rule. There is already automatic fix support for the "only one space" enforcement.

Copy link

codecov bot commented Jun 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.84%. Comparing base (dd2e968) to head (f2869fd).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3930      +/-   ##
==========================================
+ Coverage   97.73%   97.84%   +0.10%     
==========================================
  Files         136      136              
  Lines        9997    10008      +11     
  Branches     3715     3717       +2     
==========================================
+ Hits         9771     9792      +21     
+ Misses        226      216      -10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ljharb ljharb force-pushed the autocorrect-jsx-props-no-multi-spaces branch from c5974b1 to f2869fd Compare June 4, 2025 01:44
@ljharb ljharb merged commit f2869fd into jsx-eslint:master Jun 4, 2025
426 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants