issue_comments
1 row where author_association = "MEMBER", issue = 683954433 and user = 10194086 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Should __repr__ and __str__ be PEP8 compliant? · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
678703013 | https://github.com/pydata/xarray/issues/4367#issuecomment-678703013 | https://api.github.com/repos/pydata/xarray/issues/4367 | MDEyOklzc3VlQ29tbWVudDY3ODcwMzAxMw== | mathause 10194086 | 2020-08-22T22:29:31Z | 2020-08-22T22:29:31Z | MEMBER | We ignore this error here: https://github.com/pydata/xarray/blob/2bc8e33b319d54f9a6e89a88ac3161f4fb569fcf/setup.cfg#L109-L110 I think the argument is that a line lenght of 88 is much less likely to be too short: https://black.readthedocs.io/en/stable/the_black_code_style.html#line-length |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Should __repr__ and __str__ be PEP8 compliant? 683954433 |
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