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
I understand that having the output of linux commands printed to the screen is ugly to some people but for the remove command it seems very appropriate to expect the users to be able to see what they are removing. The --no-write and --verbose options do not provide useful information but instead they provide a summary. For example:
mkdir -p test/one/two
mkdir -p test/three/four
mkdir -p test/five/six
grunt clean:default --no-write --verbose
Running "clean:default" (clean) task
Verifying property clean.default exists in config...OK
Files: test -> default
Options: force=false, no-write, verbose
Not actually cleaning test...
>> 1 path cleaned.
I find the "1 path cleaned" message, while technically correct, very misleading.. Any chance we could add an actual verbose flag to grunt-contrib-clean pretty please?
The text was updated successfully, but these errors were encountered:
In an attempt to get grunt to run "rm -rvf" I can't seem to get the equivalent working with either rimraf or grunt-contrib-clean.
Supplying the --verbose to grunt does NOT supply the linux cli -v option to the rm command as expected or desired.
I'd add this request to the rimraf https://www.npmjs.com/package/rimraf package but am not sure how to.
I understand that having the output of linux commands printed to the screen is ugly to some people but for the remove command it seems very appropriate to expect the users to be able to see what they are removing. The --no-write and --verbose options do not provide useful information but instead they provide a summary. For example:
I find the "1 path cleaned" message, while technically correct, very misleading.. Any chance we could add an actual verbose flag to grunt-contrib-clean pretty please?
The text was updated successfully, but these errors were encountered: