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
When visualising the runtime benchmarks if the font is large enough there is a linebreak on the status of failed workflows, even though there is plenty of horizontal space to expand the table, see:
Although a bit less important, it would be nice if the header of the column would only break between "STATUS" and the first parenthesis when needed (see #66 (comment)).
The text was updated successfully, but these errors were encountered:
The benchmark line break is the major offender here, but if you or @kretep are looking into this, maybe also look into the column headers. The first one could use a break between "STATUS" and the first parenthesis. "PROTEINS IDENTIFIED" could be changed into "PROTEINS" and "GO-TERMS IDENTIFIED" into "GO-TERMS" to keep all column headers in two rows?
I was thinking about the same, STATUS does break in a weird way. We will look into it, but it might not be so trivial considering that the table (including the headers) is parsed from a json file. I just updated the 2 column names as you suggested.
I just looked into it and they are treated as 2 separate strings, one is the description (e.g., “status”) and the other one is units (e.g., “✓ or ✗”), so enforcing linebreak only in between the 2 should not be difficult.
When visualising the runtime benchmarks if the font is large enough there is a linebreak on the status of failed workflows, even though there is plenty of horizontal space to expand the table, see:
Although a bit less important, it would be nice if the header of the column would only break between "STATUS" and the first parenthesis when needed (see #66 (comment)).
The text was updated successfully, but these errors were encountered: