Log data can be too long #3

Closed
opened 2026-10-01 14:38:58 +03:00 by ars9 · 0 comments
Owner

When we log data blocks that are very large - it makes logs harder to read.

TODO:

  • When rendering the scenario run log block - estimate byte size AND line count of the prettified JSON
  • If it exceeds a certain limit (should be configurable, default 256 byte size, 5 line count) - hide the data block
  • There should be a toggle for data block visibility for large blocks
  • There should be a toggle that opens/closes ALL data blocks in the log (next to log section title)
  • Additionally, there should be a button to copy logs to the clipboard (it should work with the filter) next to "Download logs"
  • When copying to clipboard - the logs must be expanded (data blocks open) and readable as text
When we log data blocks that are very large - it makes logs harder to read. TODO: - When rendering the scenario run log block - estimate byte size AND line count of the prettified JSON - If it exceeds a certain limit (should be configurable, default 256 byte size, 5 line count) - hide the data block - There should be a toggle for data block visibility for large blocks - There should be a toggle that opens/closes ALL data blocks in the log (next to log section title) - Additionally, there should be a button to copy logs to the clipboard (it should work with the filter) next to "Download logs" - When copying to clipboard - the logs must be expanded (data blocks open) and readable as text
ars9 closed this issue 2026-10-02 14:12:54 +03:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ars9/liqa#3