issue_comments: 595506745
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/3596#issuecomment-595506745 | https://api.github.com/repos/pydata/xarray/issues/3596 | 595506745 | MDEyOklzc3VlQ29tbWVudDU5NTUwNjc0NQ== | 5635139 | 2020-03-06T00:04:03Z | 2020-03-06T02:08:02Z | MEMBER |
I agree, I wouldn't have expected coords to be included given existing behavior. People can switch coords <> data_vars as needed, so there's an escape hatch Edit: But it's more awkward for indexes than non-index coords. The index becomes less useful with non-unique values, and generally indexes don't have nulls. I'm not sure what the other options would be: to some extent it's the intersection of |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
532940062 |