issue_comments
2 rows where issue = 935531700 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- hooks to "prepare" xarray objects for plotting · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
873548277 | https://github.com/pydata/xarray/issues/5562#issuecomment-873548277 | https://api.github.com/repos/pydata/xarray/issues/5562 | MDEyOklzc3VlQ29tbWVudDg3MzU0ODI3Nw== | keewis 14808389 | 2021-07-04T08:46:34Z | 2021-07-04T08:46:34Z | MEMBER | that makes sense, but I think long term it might be better to find a way to delegate this to duck array extension libraries (it really should call |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
hooks to "prepare" xarray objects for plotting 935531700 | |
873478528 | https://github.com/pydata/xarray/issues/5562#issuecomment-873478528 | https://api.github.com/repos/pydata/xarray/issues/5562 | MDEyOklzc3VlQ29tbWVudDg3MzQ3ODUyOA== | keewis 14808389 | 2021-07-03T22:23:50Z | 2021-07-03T22:23:50Z | MEMBER | that will work if we want to remove the units, but |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
hooks to "prepare" xarray objects for plotting 935531700 |
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