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
Add autocorrect for control_statement #2303
Conversation
Generated by 🚫 Danger |
It’s apparent now that there’s some optimization work that needs to be done. Also, my paren matching depends on |
f2dbaf8
to
5c3be65
Compare
Codecov Report
@@ Coverage Diff @@
## master #2303 +/- ##
==========================================
+ Coverage 91.98% 92.02% +0.03%
==========================================
Files 294 294
Lines 14805 14876 +71
==========================================
+ Hits 13619 13689 +70
- Misses 1186 1187 +1
Continue to review full report at Codecov.
|
423e64b
to
9712d8e
Compare
Remove trailing whitespace introduced by Github merge & improve syntax Improve paren matching code and fix 4.0 compatibility
9712d8e
to
89c3f17
Compare
Okay, this is now in a state I would consider ready for review. Thank you for your time! |
Ugh. Something I did between "update changelog" and "optimize correction and validation" breaks autocorrect on production code, even though all the tests pass. Will investigate. |
@colejd Any updates on this? I'd be happy to review once you consider this ready for review again! |
This issue has been automatically marked as stale because it has not had any recent activity. Please comment to prevent this issue from being closed. Thank you for your contributions! |
Hello! This adds autocorrect support for the
control_statement
rule.Caveat:
As of now, it only seems to get the outermost control blocks it can find that break the rule; to fully correct, you need to run autocorrect a few times. If anyone has a way around this, I'd love to get that in here.
Thank you!