Currently if you'd like to capture the parseable output from a build, you need to handle that from stderr, and process it immediately if you want to display it for users. In some use cases it would be nice to be able to write this output to a file, while still outputting the normal output, so that file could be parsed later optionally, while not changing the normal output.
The text was updated successfully, but these errors were encountered:
I think what Keith may have meant is parseable output to file, and then using stdout/stderr for normal ("unparseable") output. In that way, you'd still see diagnostics come through the normal way, presumably for a human to read, with the full parseable info available separately to tools.