Closed tune closed 9 years ago
The Guard's default ignore patterns are applied to modified file paths detected by Guard.
With your log, RuboCop was running against all files rather than modified files by all_on_start
feature. In this case, guard-rubocop
runs rubocop
with no arguments internally, and rubocop
will find all ruby files under the current working directory so the Guard's ignore patterns won't be applied.
Though I'll consider whether guard-rubocop
should handle this case or not, I'd suggest adding some Excludes
patterns to your .rubocop.yml
like this for now.
Thank you for your quick response. Above solution meets my requirements.
In guard document, it declare that guard default setting ignore following folders.
But it seems guard-rubocop cannot ignore part of them, at least vendor/bundle.