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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When we log data blocks that are very large - it makes logs harder to read.
TODO: