issue_comments: 782739934
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/issues/4927#issuecomment-782739934 | https://api.github.com/repos/pydata/xarray/issues/4927 | 782739934 | MDEyOklzc3VlQ29tbWVudDc4MjczOTkzNA== | 6628425 | 2021-02-20T19:51:34Z | 2021-02-20T19:51:34Z | MEMBER | Yeah, I understand, these kinds of metadata issues can be frustrating to deal with, especially when things are close to being valid, but not quite. That said, I'm afraid I would be -1 on adding special logic to handle this to xarray, though I'm open to being convinced if others feel otherwise. (The time bounds logic is a bit different, because there are indeed CF Conventions pertaining to that). |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
811933067 |