issue_comments
1 row where author_association = "MEMBER", issue = 654135405 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- Add cupy support · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
660297175 | https://github.com/pydata/xarray/issues/4212#issuecomment-660297175 | https://api.github.com/repos/pydata/xarray/issues/4212 | MDEyOklzc3VlQ29tbWVudDY2MDI5NzE3NQ== | keewis 14808389 | 2020-07-17T19:26:14Z | 2020-07-17T19:26:14Z | MEMBER |
actually, I have been able to get by without compatibility code, the code changes outside of While adding support for While there are parts where interaction between Ideally, to make those work we'd have a standard on how to explicitly get the data of a duck array as a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add cupy support 654135405 |
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