issue_comments
2 rows where author_association = "MEMBER", issue = 565626748 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- `where` ignores incorrectly typed arguments · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
586655557 | https://github.com/pydata/xarray/issues/3770#issuecomment-586655557 | https://api.github.com/repos/pydata/xarray/issues/3770 | MDEyOklzc3VlQ29tbWVudDU4NjY1NTU1Nw== | max-sixty 5635139 | 2020-02-16T00:34:27Z | 2020-02-16T00:34:27Z | MEMBER | 👍 a) should we type check before we pass to numpy? b) should we support single-argument callables? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`where` ignores incorrectly typed arguments 565626748 | |
586547352 | https://github.com/pydata/xarray/issues/3770#issuecomment-586547352 | https://api.github.com/repos/pydata/xarray/issues/3770 | MDEyOklzc3VlQ29tbWVudDU4NjU0NzM1Mg== | max-sixty 5635139 | 2020-02-15T03:07:14Z | 2020-02-15T03:07:14Z | MEMBER | Would we want callables to be acceptable arguments to functions like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`where` ignores incorrectly typed arguments 565626748 |
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