Closed roman-kruglov closed 2 years ago
I have several more ideas regarding this and simple output too, I'll have more improvements
I've added a change that groups up all the targets into an object to simplify parsing (you can safely iterate on all keys in targets json object instead of having to filter root keys), please be aware
I've added a change that groups up all the targets into an object to simplify parsing (you can safely iterate on all keys in targets json object instead of having to filter root keys), please be aware
yep, was thinking about combining targets for this same purpose too
so the whole report goes as one log entry with a JSON object for each target
Description
This might be helpful for logging and assessing to have the whole summary report as one entry. Though arguably it makes it even less readable in terminal's output, and I tried to improve that with pr #517. I tried to make
zap
pretty print this huge JSON report object (for the case when-log-format simple
from #517), but it was way too complicated for such a simple feature. Though it might still be possible.What do you guys think? Could this be helpful?
Type of change
Potentially somebody could rely on the current summary format, but with so many swift changes and the recent move to
zap
- I doubt it.How Has This Been Tested?
By running and looking at the output in a terminal.
Test Configuration
Logs
Output sample (real values crossed out, truncated for shorter text)
the full log entry with the current default format would look like this: