issue_comments: 325738019
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/1528#issuecomment-325738019 | https://api.github.com/repos/pydata/xarray/issues/1528 | 325738019 | MDEyOklzc3VlQ29tbWVudDMyNTczODAxOQ== | 1197350 | 2017-08-29T17:35:09Z | 2017-08-29T17:35:09Z | MEMBER | One path forward for now would be to ignore the filters like If we think there is an advantage to using the zarr native filters, that could be added via a future PR once we have the basic backend working. @alimanfoo: when do you anticipate the 2.2 zarr release to happen? Will the API change significantly? If so, I will wait for that to move forward here. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
253136694 |