quiet / minimal output mode

[joprice]

I have been using Fun.Build extensively as a build and ci pipeline dsl. It may be an abuse of the tool, but it's quite convenient. I have an DU Project with cases FableProject and Native I use to abstract over common command patterns.

For one case, I run a job system that locally starts processes manually by running the build script. This is convenient since I can change the job code and get feedback when the job kicks off, always using the latest code in dev. However, the logging output with large ascii font and run stages becomes a bit cumbersome to sift through when there's an important log or error. What do you think of a --quiet flag to optionally suppress logging or make it more compact?

[albertwoo]

Good idea. Do you want to implement it?

[joprice]

Yup, I can take a shot at it.

[joprice]

I haven't had time to work on this (as it's not pressing, just a nice to have), but noticed that another smaller tweak could be adding a quiet or silent argument to RunCommandCaptureOutput, where the command is currently always printed - AnsiConsole.WriteLine commandStr.

I hit this when trying to print a table of deployment status over different projects, where the command output gets interleaved with the task's output.

[albertwoo]

Yes, we can add a optional argument for that. I will do it.

[albertwoo]

disablePrintCommand is added in 1.1.16