Before, it could happen that a child doesn't have a value, so it would
be omitted from the summary. Similarly, it can happen that a child
doesn't have a summary but has a value.
Now, we first try the summary and fall back to the value.
Without this change, when printing this struct in a log point using "foo is {foo}" we would just get "foo is {...}":
struct Foo {
bar: String,
}
With the fix, we get "foo is {bar:"a string"}"
While we were at it, we also bumped MAX_LENGTH to 512 but I'm not married to that.
Before, it could happen that a child doesn't have a value, so it would be omitted from the summary. Similarly, it can happen that a child doesn't have a summary but has a value.
Now, we first try the summary and fall back to the value.
Without this change, when printing this struct in a log point using
"foo is {foo}"
we would just get"foo is {...}"
:With the fix, we get
"foo is {bar:"a string"}"
While we were at it, we also bumped
MAX_LENGTH
to 512 but I'm not married to that.