issue_comments
2 rows where issue = 264747372 and user = 6815844 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- html repr of xarray object (for the notebook) · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
336488056 | https://github.com/pydata/xarray/issues/1627#issuecomment-336488056 | https://api.github.com/repos/pydata/xarray/issues/1627 | MDEyOklzc3VlQ29tbWVudDMzNjQ4ODA1Ng== | fujiisoup 6815844 | 2017-10-13T15:36:13Z | 2017-10-13T15:36:13Z | MEMBER |
I like this idea. Looking forward to having it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
html repr of xarray object (for the notebook) 264747372 | |
336471850 | https://github.com/pydata/xarray/issues/1627#issuecomment-336471850 | https://api.github.com/repos/pydata/xarray/issues/1627 | MDEyOklzc3VlQ29tbWVudDMzNjQ3MTg1MA== | fujiisoup 6815844 | 2017-10-13T14:38:12Z | 2017-10-13T14:38:12Z | MEMBER | This is wonderful! Is it reasonable to add a drop down in the attribute section if there are too many items there? My data sometimes have a long list of attributes and important information about coordinate and data_vars are not seen without scrolling back the page. (This may be a rare case though...) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
html repr of xarray object (for the notebook) 264747372 |
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