issue_comments

Table actions

where issue = 35682274 and user = 1217238 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
254680423 https://github.com/pydata/xarray/issues/158#issuecomment-254680423 https://api.github.com/repos/pydata/xarray/issues/158 MDEyOklzc3VlQ29tbWVudDI1NDY4MDQyMw== shoyer 1217238 2016-10-19T00:49:27Z 2016-10-19T00:49:27Z MEMBER

This issue dates to very early in the days of xarray, before we even had a direct DataArray constructor. I have no idea exactly what I was thinking here.

I agree, it would be more consistent and user friendly to pick a default name for the group (maybe 'group'). Any interest in putting together a PR?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   groupby should work with name=None 35682274

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