Warn when --exclude
///> using exclude
does not actually exclude any files from the project
#3387
Labels
--exclude
Issues tied with the excluding inputs.
enhancement
New feature or request
reporting
Issues tied with error and warning reporting.
spree
UX
Version(s)
1.5.4 and 4ab3227
Describe the issue
When declaring a path or pattern in
--exclude
///> using exclude
, I'd like a warning if no sources were actually caught by the pattern I declared. This would make it easier to catch when my exclusion actually works.Additionally, I'd like some debug logs under
-v -v -v
telling me which files were, in fact, excluded.The text was updated successfully, but these errors were encountered: