Closed eduardRsult closed 1 year ago
@eduardRsult Are you using .stringify(value, null, 2)
before logging the objects to the log? If so, that could be the issue.
Yes sometimes the module I use spits that out. Or it is added instead of the default toString() method to error objects since they are sometimes not only thrown but also saved.
Is there a way you could handle this like the other plugin? It's valid JSON after all.
Yeah, I'll see what I can do
I found a solution. It'll be in the next release (ETA a few days).
I submitted a new release to the Chrome Web Store. It'll be available whenever Google approves it.
Update: It's been approved.
Describe the bug A clear and concise description of what the bug is.
Answer: In script executions logs some json gets beautified some does not. Previously only JOSN that was inclomplete (cutoff by log details character limit) was not beautified. Now it just parses some and some not.
How to reproduce _Describe steps to reproduce the behavior. Run a map reduce that creates many logs with json. Some longer some shorter.
Expected behavior A clear and concise description of what you expected to happen. All json beautified
Screenshots I have 2 (arbitrary) situations
I made screenshots for each of them in 3 conditions
Additional context I am pretty sure this worked better before. Nice that the scriptIds are clickable to the record type. Would be great to have an easy way to link to an instance like discussed on Linkedin