issue_comments
2 rows where issue = 628719058 and user = 4160723 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Feature Request: Hierarchical storage and processing in xarray · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
905427176 | https://github.com/pydata/xarray/issues/4118#issuecomment-905427176 | https://api.github.com/repos/pydata/xarray/issues/4118 | IC_kwDOAMm_X84197jo | benbovy 4160723 | 2021-08-25T11:47:10Z | 2021-08-25T11:47:10Z | MEMBER | Great work @TomNicholas! For rich/html reprs, I think that we could take much inspiration from some of the dask reprs shown in this blog post. I haven't looked at your repository in detail yet, but I have one general question about the design: what is the rationale of having two separate classes |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Feature Request: Hierarchical storage and processing in xarray 628719058 | |
801785278 | https://github.com/pydata/xarray/issues/4118#issuecomment-801785278 | https://api.github.com/repos/pydata/xarray/issues/4118 | MDEyOklzc3VlQ29tbWVudDgwMTc4NTI3OA== | benbovy 4160723 | 2021-03-18T09:54:42Z | 2021-03-18T09:54:42Z | MEMBER | FWIW, a while ago I wrote a mock-up (and probably outdated) https://gist.github.com/benbovy/92e7c76220af1aaa4b3a0b65374e233a (nbviewer link) |
{ "total_count": 3, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 3, "rocket": 0, "eyes": 0 } |
Feature Request: Hierarchical storage and processing in xarray 628719058 |
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