On Thu, 2024-01-11 at 14:28 +, John Barrow wrote:
> You deduced correctly that it would mean introducing a debug line to
> publish the Object at that time if you are debugging within one of
> their methods, although if you are doing that you must have a
> compilable source.
Yes, I've got the
Hi,
> Does this still requires me to change the source code? It looks like it
to me though I might be missing something.
You deduced correctly that it would mean introducing a debug line to
publish the Object at that time if you are debugging within one of their
methods, although if you are doin
Hi John,
On Tue, 2024-01-09 at 17:00 +, John wrote:
> Hi,
>
> Firstly, I believe the etiquette is to always use “Reply All” so that
> the rest of the group is aware of the thread progression.
Sorry about that. My mail agent (Evolution) didn't recognise your
message as coming from a mail li
nting(); return gsonBuilder.create().toJson(object); } And so you could use that in your code to publish the nested array to a log or System.out() John From: Admin @ GoodunSent: 09 January 2024 15:06To: JohnSubject: Re: Variable display in debugger That's great. but it seems to rely on
Hi, I make use of the Debuggers ‘Variables’ tab and make the ‘String value: String representation of the value” column active. For some reason it is off by default. Then, for any complex class I ensure that the @Override public String toString() {} method is defined to publish all the details about
