issue_comments
2 rows where issue = 415209776 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- formatting of singleton DataArrays · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
469325571 | https://github.com/pydata/xarray/issues/2791#issuecomment-469325571 | https://api.github.com/repos/pydata/xarray/issues/2791 | MDEyOklzc3VlQ29tbWVudDQ2OTMyNTU3MQ== | shoyer 1217238 | 2019-03-04T16:48:03Z | 2019-03-04T16:48:03Z | MEMBER | Here's a related NumPy issue: https://github.com/numpy/numpy/issues/5543 I guess there are two possible behaviors for These behaviors would definitely conflict for scalar objects -- in the second case, we would still want to include some indication that it's an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
formatting of singleton DataArrays 415209776 | |
469155529 | https://github.com/pydata/xarray/issues/2791#issuecomment-469155529 | https://api.github.com/repos/pydata/xarray/issues/2791 | MDEyOklzc3VlQ29tbWVudDQ2OTE1NTUyOQ== | shoyer 1217238 | 2019-03-04T08:05:53Z | 2019-03-04T08:05:53Z | MEMBER | Yes, I think this would be a nice addition. This would entail implementing a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
formatting of singleton DataArrays 415209776 |
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