Page MenuHomePhabricator

Remove "--lintall" and "--only-new" flags to "arc diff"
ClosedPublic

Authored by epriestley on May 30 2020, 9:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 15, 2:47 PM
Unknown Object (File)
Mon, Nov 11, 3:01 AM
Unknown Object (File)
Wed, Oct 30, 8:28 AM
Unknown Object (File)
Fri, Oct 25, 1:03 AM
Unknown Object (File)
Oct 13 2024, 9:52 PM
Unknown Object (File)
Oct 1 2024, 6:44 AM
Unknown Object (File)
Sep 29 2024, 10:50 AM
Unknown Object (File)
Sep 23 2024, 4:37 PM
Subscribers
None

Details

Summary

Ref T13544. These flags change the behavior of the "arc lint" subprocess.

I believe there is no reason to ever use "arc diff --lintall". If you want to find extra warnings to fix, you can use "arc lint --lintall" to express this intent.

Use of "arc diff --only-new" almost certainly means your linters are raising messages at "error" severity which should instead be raised at "warning" severity. If you only care about fixing a particular type of error in changed code, it should be raised as a "warning". The correct remedy is to adjust the severity, not use "--only-new", which is a very broad, slow, complicated hammer.

Test Plan

Searched for "lintall" and "only-new" in this workflow. These flags still exist in "arc lint", but may be changed in the future. Generated this change.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Jun 5 2020, 8:24 PM
This revision was automatically updated to reflect the committed changes.