issue_comments
1 row where author_association = "MEMBER" and issue = 433703713 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Explicit fixed width 'S1' arrays re-encoded creating extra dimension · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
484158566 | https://github.com/pydata/xarray/issues/2899#issuecomment-484158566 | https://api.github.com/repos/pydata/xarray/issues/2899 | MDEyOklzc3VlQ29tbWVudDQ4NDE1ODU2Ng== | shoyer 1217238 | 2019-04-17T16:15:29Z | 2019-04-17T16:15:29Z | MEMBER | This has some overlap with the proposal in https://github.com/pydata/xarray/issues/2895 I don't think there's an option to disable this currently, but it would probably make sense to add one. In the past, we may not have created dummy dimenisons if the string already had dtype |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit fixed width 'S1' arrays re-encoded creating extra dimension 433703713 |
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