issue_comments
1 row where issue = 181340410 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
These facets timed out: issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
605453650 | https://github.com/pydata/xarray/issues/1040#issuecomment-605453650 | https://api.github.com/repos/pydata/xarray/issues/1040 | MDEyOklzc3VlQ29tbWVudDYwNTQ1MzY1MA== | max-sixty 5635139 | 2020-03-28T14:20:49Z | 2020-03-28T14:20:49Z | MEMBER | I'm low confidence keener on a consistent API that doesn't depend on the number of dimensions, rather than saving a kwarg, so would vote +0.1 on retaining the implementation and changing the docstring, such that it's required to pass a dimension name even with one dimension. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray.diff dim argument should be optional as is in docstring 181340410 |
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