issue_comments: 325066185
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/1473#issuecomment-325066185 | https://api.github.com/repos/pydata/xarray/issues/1473 | 325066185 | MDEyOklzc3VlQ29tbWVudDMyNTA2NjE4NQ== | 1217238 | 2017-08-26T00:52:03Z | 2017-08-26T00:52:03Z | MEMBER | Thinking about this more: I still think I would prefer including all coordinates from indexers unless there is already an existing coordinates of the same name. Reasons why I like this rule:
1. It's simple and easy to explain, without any special cases.
2. If the coordinates are descriptive of the indexers, I think they're almost certainly still descriptive of the indexed results.
3. Users seem to be happier with keeping around metadata (e.g., |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
241578773 |