You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The preprocessing functions were too unwieldy to leave them on the
command line. This makes it possible to run any lint check directly from
the command line before committing code.
Co-authored-by: Michael Chirico <chiricom@google.com>
Copy file name to clipboardExpand all lines: .ci/README.md
+5-15Lines changed: 5 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,25 +55,15 @@ Base R runner for the manual (non-`lintr`) lint checks to be run from GitHub Act
55
55
1. Path to the directory containing files defining the linters. A linter is a function that accepts one argument (typically the path to the file) and signals an error if it fails the lint check.
56
56
2. Path to the directory containing files to check.
57
57
3. A regular expression matching the files to check.
58
-
4. An R expression evaluating to a function that processes a single file path into a form understood by the lint functions. Additionally, the function may return `NULL` to indicate that the file must be skipped.
58
+
59
+
One of the files in the linter directory may define the `.preprocess` function, which must accept one file path and return a value that other linter functions will understand. The function may also return `NULL` to indicate that the file must be skipped.
59
60
60
61
Example command lines:
61
62
62
63
```sh
63
-
# C linters expect a three-element named list, not the file path
0 commit comments