shorebirdtech
fix: Shorebird disables gradle println
Description
I have println calls in my build.gradle. Using shorebird, these are not seen in the console.
-v doesn't work.
shorebird just calls out to flutter build under the covers. You can try running with -v to see all the commands shorebird is executing. Presumably we're just not piping the prints through.
shorebirdjust calls out toflutter buildunder the covers. You can try running with-vto see all the commandsshorebirdis executing. Presumably we're just not piping the prints through.
I have used -v, see initial comment.
I believe we only forward verbose output when the invoked command fails (https://github.com/shorebirdtech/shorebird/blob/main/packages/shorebird_cli/lib/src/process.dart#L213-L214). I forget the exact conversation that led to this decision, but I believe we were trying to balance signal-to-noise in the logs (as verbose is very verbose)
But either way, invoking the flutter build command manually should print what you want to see
It's possible the right solution would be to add an extra level (or levels) of verbosity to the CLI that would log stdout/stderr regardless of whether the invoked command failed.
Given the amount of data output
trying to balance signal-to-noise in the logs (as verbose is very verbose)
Agreed on the amount of data being outputted, but it's that way for a reason. Given the sheer amount of different systems interacting, too much information is better than not enough. Different levels of verbosity can be applied, but I would default to what the different underlying systems do by default too.
Presumably the solution here is to add another layer of verbosity as bryan suggests.
Context:
Since this was filed, we've updated the CLI to pass the --verbose flag to flutter when it's passed to the CLI. We (I think I was the one who did this, but not sure) originally tried passing --verbose to every command, but not all of our CLI artifacts recognize --verbose. I forget which, but some expect -verbose and some only recognize -v.