Add "### Fast Compile >> .....ts" behind verbose flag, or add silent flag?

[ThaNarie]

Hi,

One of the usages of grunt-ts is to compile 'generated' typescript files by a task that rune before this so all code is valid js.

For example:

scaffold:
  - 'scaffold-pages'
  - 'ts'
  - 'sass'
  - 'autoprefixer'

...
### Fast Compile >>deploy/htdocs/inc/script/test/jasmine-matchers.d.ts 
### Fast Compile >>deploy/htdocs/inc/script/test/jasmine.d.ts          
### Fast Compile >>deploy/htdocs/inc/script/test/testSpec.ts           
...

But because the output of grunt-ts is so 'long', as a user you are missing the output of the 'main' task (scaffold-pages).

It would be awesome if we can configure the verbosity of the task, either by putting this output behind the verbose option, or maybe adding a silent option to keep this the default but providing an option to keep it quiet :)

I'm open for providing a PR if desired, but just wanted to know if you're up to this idea and which of the above would be the best approach.

[basarat]

It would be awesome if we can configure the verbosity of the task,

Do-able without an option > If the count of the filtered files for fast compile equate the original file count > means we are not actively fast compiling and don't output these file names. PR much appreciated.

[ThaNarie]

Looking at the docs again, I guess I should just set fast to "never" as it will never fast compile when doing a 'stand-alone' grunt-ts from the command-line, and just re-generates the cache every time.

But a change in output when people like me are leaving the option to the default value could still be a good addition, so I might look into that :)

[basarat]

But a change in output when people like me are leaving the option to the default value could still be a good addition, so I might look into that

👍 leaving this issue open for a hero

[0815fox]

+1 I would also like to have that, however, until end of this year I might be too busy to look into that.

[JoshuaKGoldberg]

Dear god do want. +1.

I just converted a problem from old-style /// <reference path="..." />s to imports and the wall of blue is very disorienting.

[nycdotnet]

I do intend to fix this - in the meantime it should be fairly straight forward to comment out the line that outputs it - it should be around line 39 in compile.js, depending on which version you have.