Make 'yarn lint --fix' work as an alias to 'yarn lint-fix'.

[fqueze]

Because I'm so used to mach lint --fix, I keep running yarn lint --fix when I need yarn lint-fix. Making yarn lint --fix work seems easier than fixing my muscle memory.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.84%. Comparing base (531ad81) to head (9eccc42).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5563   +/-   ##
=======================================
  Coverage   85.84%   85.84%           
=======================================
  Files         309      309           
  Lines       30338    30338           
  Branches     8346     8346           
=======================================
  Hits        26045    26045           
  Misses       3873     3873           
  Partials      420      420           

☔ 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.

[mstange]

I agree that yarn lint --fix should work.

But I don't think that script is the right place - this is affecting the input, not the output. I think it might be better to have a separate lint.ts script in the scripts directory which replaces the run-p in the current lint command, i.e. which manually fans out to the other lint commands and passes --fix to all if it is run with --fix. Or maybe there's a way to get run-p to do this automatically?

[fqueze]

I agree that yarn lint --fix should work.

But I don't think that script is the right place - this is affecting the input, not the output. I think it might be better to have a separate lint.ts script in the scripts directory which replaces the run-p in the current lint command, i.e. which manually fans out to the other lint commands and passes --fix to all if it is run with --fix. Or maybe there's a way to get run-p to do this automatically?

If it's the "output" word in the "bin/output-fixing-commands.js" name that worries you, we could also just rename that script to "fix-commands.js". I think that script is a place that makes some sense as it's where we already handle something else related to lint "fix". But I'm not opposed to creating a separate script either.

[mstange]

I'm fine with landing this as is. I looked into fixing it a different way but ended up reworking a whole bunch of stuff so let's just take the simple form to get the immediate benefit.

[mstange]

After thinking about it more I think the word "output" here is actually used as a verb, not as a noun. As in "print the corresponding fixing command to console"