Uploaded image for project: 'Yetus'
  1. Yetus
  2. YETUS-461

Allow specifying exclusions for whitespace report

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.4.0
    • Component/s: Precommit
    • Labels:
      None
    • Release Note:
      Hide
      <!-- markdown -->
      Apache Yetus Precommit users can specify a list of filename regexes to ignore when checking for whitespace errors with the new command line arguments:

      * `--whitespace-eol-ignore-list` to skip end-of-line whitespace checks
      * `--whitespace-tabs-ignore-list` to skip checking for tabs
      Show
      <!-- markdown --> Apache Yetus Precommit users can specify a list of filename regexes to ignore when checking for whitespace errors with the new command line arguments: * `--whitespace-eol-ignore-list` to skip end-of-line whitespace checks * `--whitespace-tabs-ignore-list` to skip checking for tabs

      Description

      I have this in my report:

      -1	whitespace	0m 0s	The patch has 2298 line(s) that end in whitespace. Use git apply --whitespace=fix.
      

      The 2298 lines are from files generated by protoc. I could try fixing protoc to not add the odd space at the end of a line but other tools than protoc probably have this tick.

      It would be sweet if I could configure the whitespace tooling passing a list of regexes to exclude when generating the report (Sean suggest it be a command-line config and told me file this issue). Thanks.

        Attachments

        1. YETUS-461.00.patch
          3 kB
          Kengo Seki

          Activity

            People

            • Assignee:
              sekikn Kengo Seki
              Reporter:
              stack Michael Stack
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: