issue_comments: 296787111
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/1252#issuecomment-296787111 | https://api.github.com/repos/pydata/xarray/issues/1252 | 296787111 | MDEyOklzc3VlQ29tbWVudDI5Njc4NzExMQ== | 2443309 | 2017-04-24T18:47:24Z | 2017-04-24T18:47:24Z | MEMBER | My two cents. I think we want:
Presumably, we can address many of the negatives with this approach with follow-on PRs. The fallback logic in xarray right now for non-standard calendars is not something we want to keep and was mostly meant as a stop-gap until this feature came along. |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
205473898 |