TallTed
commented
1 year ago A couple of alternatives/enhancements to the original request. The value of any of these, including the original request, depends on the deployment/use-case.
-
A left-end truncation (
...xyz) can be more helpful than right-end (abc...) -
A mid-value truncation (
abc...xyz) can be more helpful than truncating either end -
Wrapping long values (so making the key+value multiple lines tall, optimally with the key aligned to the top of the value by default, optimally with a switch that aligns key+value at middle, or even bottom) can be more helpful than any truncation
If any of these are implementable along with the original request (right-end truncation), the user would optimally be able to control which is active via a live-UI switch, which might persist from use to use via a persistent preference-file setting. Such preference-file setting might be used instead of live-UI switch, if the latter is difficult to implement.
aatbip
faizanu94
AykutSarac
Feature
If a JSON field contains long strings the diagram becomes extremely small. For instance
User needs to see trimmed version of a long text
Cut off no more than 50 symbols with ... at the end.
Alternative solutions or implementations
No response
Other context
No response