issue_comments
1 row where author_association = "CONTRIBUTOR", issue = 500949040 and user = 1956032 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Recommendations for domain-specific accessor documentation · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
537669216 | https://github.com/pydata/xarray/issues/3361#issuecomment-537669216 | https://api.github.com/repos/pydata/xarray/issues/3361 | MDEyOklzc3VlQ29tbWVudDUzNzY2OTIxNg== | gmaze 1956032 | 2019-10-02T20:35:26Z | 2019-10-02T20:35:26Z | CONTRIBUTOR | Thanks for the example @jthielen, this looks great ! May be it would be better to not show to readers the accessor class name, since it will never be seen on the API frontend, only the scope name will. So it would be great to be able to have the documentation to read something like:
instead of:
But I don't know how to manage that with sphinx documentation |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Recommendations for domain-specific accessor documentation 500949040 |
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