BigRoy
commented
1 year ago I just wanted to add a side note that a lot of the logs in your screenshot should be debug logs instead of info logs.
Anything that is info level or higher should be artist-facing reports and should be understandable, informative, and preferably describe a course of action on what they should do with that information.
E.g. all of these should be debug logs:
And these should provide more information as to what that means:
Missing values? What does that mean? What can the user do about it?
And these also feel like debug logs to me:
We want to reduce the reports to only contain the standout information that helps the artists. We've found that providing these detailed logs like they are now is so much clutter that artists even start ignoring warning and error logs that might be crucial for them to be aware of.
Nevertheless the report should indeed not be cut off, thanks for the report! :)
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
The publish report are being cut off.
How would you imagine the implementation of the feature?
Either a horizontal scroll bar or word wrap the text.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
[cuID:OP-6368]