I prefer the latter. Thanks, Akira
On Sun, Feb 17, 2019 at 4:38 AM Allen Wittenauer <a...@apache.org> wrote: > > > I’m implementing the latter as YETUS-794. > > > > On Feb 8, 2019, at 8:54 AM, Allen Wittenauer <a...@apache.org> wrote: > > > > > > Hi. > > > > In some of the source trees I’m working with, there are a bunch of > > imported files from other places that we don’t technically control (e.g., > > vendor files). Needless to say, the files don’t conform to what Yetus > > thinks is quality content and need to be excluded from the tests. > > Originally I was thinking that we would add an exclusion file for each > > test. But now I’m thinking we would be better off just having one big one > > that we could apply to as many outputs as possible: > > > > For example: > > > > Per-test > > > > --shellcheck-exclude=/path/to/list > > --pylint-exclude=/path/to/list > > --rubocopy-exclude=/path/to/list > > > > Global > > > > --exclude-list=/path/to/list > > > > Thoughts? >
