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
I know it is maybe bad practise, but when I am doing it, some other user might too:
I do store some very long JSON-strings or other long text content in some objects for debugging or to be reused.
These long object contents seem to bring the object-tab to it's knees, when the object-tree is extended to display these long-length objects.
Description
To avoid this problem, and as noone is able to see the full value of an object unless he clicks on the value itself or copies it, we might limit the preloaded value-string-length and only fetch the full content when it is really to be displayed in full.
Additional context
No response
The text was updated successfully, but these errors were encountered:
It is fast now, as intended, but if you click on the copy icon, it should load the full string though. Is this possible? Otherwise, I would keep it as before, because a reliable copy command is more important than performance in edge-cases....
No existing issues.
Related problems
I know it is maybe bad practise, but when I am doing it, some other user might too:
I do store some very long JSON-strings or other long text content in some objects for debugging or to be reused.
These long object contents seem to bring the object-tab to it's knees, when the object-tree is extended to display these long-length objects.
Description
To avoid this problem, and as noone is able to see the full value of an object unless he clicks on the value itself or copies it, we might limit the preloaded value-string-length and only fetch the full content when it is really to be displayed in full.
Additional context
No response
The text was updated successfully, but these errors were encountered: