issue_comments: 904000203
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/pull/5662#issuecomment-904000203 | https://api.github.com/repos/pydata/xarray/issues/5662 | 904000203 | IC_kwDOAMm_X8414fLL | 14371165 | 2021-08-23T18:13:54Z | 2021-08-23T18:13:54Z | MEMBER | It was easy enough to change so here's how it would look like with one of these extreme datasets: Original:
New line with some indent:
No new line but small indent:
I think I prefer the original one because of the alignment with the dims in coords and data variables. The second one is nice, familiar format as Coordinates and will likely never get in to the 1 long dimension per row issue like in one of the examples. But it looks a little too dense now maybe? This is also adds an extra row for all cases which might not be necessary with most real life datasets? Dimensions without coordinates will add 1 extra row as well. The 3rd one was an alternative to avoid a completely breaking change like the second one is. But I think it looks the worst of these alternatives, too messy. But it's similar to how it looks like right now if the console wraps the printed text. On another note I'm slightly annoyed that the attribute values aren't aligning the same way as coords and data variables and I cannot unsee it now. :/ |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
957439114 |