issue_comments
2 rows where issue = 105673104 and user = 9342082 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Adding a generalized 1D plotting function · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
141567421 | https://github.com/pydata/xarray/pull/566#issuecomment-141567421 | https://api.github.com/repos/pydata/xarray/issues/566 | MDEyOklzc3VlQ29tbWVudDE0MTU2NzQyMQ== | drewokane 9342082 | 2015-09-18T20:57:33Z | 2015-09-18T20:57:33Z | NONE | The only error left that is failing is testing if the ylabel in the histogram contains the word 'Count'. If we're moving towards a generalized plotting function, we need to rethink labeling the axes. Thoughts? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Adding a generalized 1D plotting function 105673104 | |
140233059 | https://github.com/pydata/xarray/pull/566#issuecomment-140233059 | https://api.github.com/repos/pydata/xarray/issues/566 | MDEyOklzc3VlQ29tbWVudDE0MDIzMzA1OQ== | drewokane 9342082 | 2015-09-14T23:32:38Z | 2015-09-14T23:32:38Z | NONE | Do I need to address the Travis-CI errors? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Adding a generalized 1D plotting function 105673104 |
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