Processing the displayed entry while keeping the original untouched?


Author
Message
Zoltan Kelemen
Zoltan Kelemen
I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)I'm into this (229 reputation)
Group: Forum Members
Posts: 21, Visits: 97
Hi!

I've started playing around with building custom extensions, even though I'm not exactly a coder, so it's a bit stabbing around in the dark Smile

Since this particular issue I'm approaching has rather long / complex message parts, my goal is to improve the message as it is displayed in the Log Entry Box (bottom right). I was able to use a post processor to massage the data into a shape, that can be handled better by the JSON pretty printer, however, I had to modify LogEntry.OriginalLogEntry for this.

However, Ideally I'd like to keep the original log entry as it is, so that I'm able to copy out log lines for reference.
(i.e. I would like to benefit from the high readability of the pretty printed entries for my own analysis, but when opening bugs, I can easily clip the original log entries as they were logged, to avoid arguments with developers BigGrin )

In short, is it possible to keep the cake and eat it too? BigGrin

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Login

Explore
Messages
Mentions
Search