Difference in JSON vs Text Output

Just started experimenting with the latest release (2.0.4.18 (2.0.4.18_canary_2019-05-12)) and noticed a difference in email reporting notation:

In the “classic” text email output the run times were displayed in both text and epoch formats, as in:

EndTime: 5/20/2019 6:30:25 AM (1558351825)
BeginTime: 5/20/2019 6:30:00 AM (1558351800)

In the new JSON output format the time stamps are shown in RFC 3339 format:

"EndTime":"2019-05-19T22:42:53.5702498Z",
"BeginTime":"2019-05-19T22:42:52.5792596Z",

Is this the new format for date/time display going forward or should the epoch notation also be added to the JSON output?

Not sure I have an opinion on this one, I just need to know so dupReport can handle all potential formats appropriately.

Thanks,

HG

I think RFC 3339 is just the default way C# converts timestamps to json strings.

It’s not very reader friendly, but I guess the json report is more meant for parsing than reading.

Unless there is a good reason I think it’s best just leaving json output as is :slight_smile:

1 Like

That reasoning sounds good enough for me. Thanks.