issue_comments
1 row where author_association = "MEMBER", issue = 102703065 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Support for netcdf4/hdf5 compression · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
134279075 | https://github.com/pydata/xarray/issues/548#issuecomment-134279075 | https://api.github.com/repos/pydata/xarray/issues/548 | MDEyOklzc3VlQ29tbWVudDEzNDI3OTA3NQ== | shoyer 1217238 | 2015-08-24T16:18:00Z | 2015-08-24T16:18:00Z | MEMBER | This is actually already supported, though poorly documented (so it's basically unknown). We seem to have some sort of bug in our documentation generation for recent versions, but in the v0.5.1 IO docs, you can see the The way this works is that Because encoding is read in when files are opened, invalid encoding options are currently ignored when saving a file to disk. This means that the current API is not very user friendly. So I'd like to extend this into a keyword argument |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Support for netcdf4/hdf5 compression 102703065 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 1