Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[enhancement]: In object-tab, limit displayed object value-length for performance reasons #2924

Open
1 task done
seb2010 opened this issue Jan 25, 2025 · 2 comments
Open
1 task done

Comments

@seb2010
Copy link

seb2010 commented Jan 25, 2025

No existing issues.

  • There is no existing issue for my request.

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

@GermanBluefox
Copy link
Contributor

Please test with admin 7.4.17

@seb2010
Copy link
Author

seb2010 commented Jan 26, 2025

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....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants