issue_comments
2 rows where issue = 186868181 and user = 1310437 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- DataArray.apply is missing · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
258425477 | https://github.com/pydata/xarray/issues/1074#issuecomment-258425477 | https://api.github.com/repos/pydata/xarray/issues/1074 | MDEyOklzc3VlQ29tbWVudDI1ODQyNTQ3Nw== | burnpanck 1310437 | 2016-11-04T13:04:37Z | 2016-11-04T13:04:37Z | CONTRIBUTOR | As for the consistency concern, I wouldn't have expected that to be a big issue. I'd argue that most functions mapping |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray.apply is missing 186868181 | |
258423515 | https://github.com/pydata/xarray/issues/1074#issuecomment-258423515 | https://api.github.com/repos/pydata/xarray/issues/1074 | MDEyOklzc3VlQ29tbWVudDI1ODQyMzUxNQ== | burnpanck 1310437 | 2016-11-04T12:55:15Z | 2016-11-04T12:55:15Z | CONTRIBUTOR | Aha! For my use-case, |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray.apply is missing 186868181 |
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