You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes 20 characters is not enough for a value. A datetime with timezone, for example, is rendered as "2018-01-01 12:00:00+ ...". In other cases the value could be best rendered as a multiline string.
It would be nice to be able to influence the reporter in this way.
The text was updated successfully, but these errors were encountered:
Yeah, I guess that can be increased and even apply a dynamic cut size depending on the value length. E.g: if len(x) < 50 display all else cut to 40 characters.
This size has been raised to 50 characters in #64 .
It seems to be enough to have complete datetimes and enough objects string representation to be relevant.
Sometimes 20 characters is not enough for a value. A datetime with timezone, for example, is rendered as
"2018-01-01 12:00:00+ ..."
. In other cases the value could be best rendered as a multiline string.It would be nice to be able to influence the reporter in this way.
The text was updated successfully, but these errors were encountered: