issue_comments

Table actions

1 row where issue = 181340410 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • keewis · 1 ✖

issue 1

  • DataArray.diff dim argument should be optional as is in docstring · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
605444025 https://github.com/pydata/xarray/issues/1040#issuecomment-605444025 https://api.github.com/repos/pydata/xarray/issues/1040 MDEyOklzc3VlQ29tbWVudDYwNTQ0NDAyNQ== keewis 14808389 2020-03-28T12:56:37Z 2020-03-28T12:56:37Z MEMBER

this is still relevant. Should we update the docstring or the implementation? If we choose the latter we might be able to pick the commit by @smartass101 (or he might open a PR for it if he's still around?)

 
{
    "total_count": 0,
    "+1": 0,
    "-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

CSV options: 

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]);