issue_comments

Table actions

1 row where issue = 435330735 and user = 10050469 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

  • fmaussion · 1 ✖

issue 1

  • docs questions from new user · 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
486999992 https://github.com/pydata/xarray/issues/2909#issuecomment-486999992 https://api.github.com/repos/pydata/xarray/issues/2909 MDEyOklzc3VlQ29tbWVudDQ4Njk5OTk5Mg== fmaussion 10050469 2019-04-26T09:51:38Z 2019-04-26T09:51:38Z MEMBER

too many references to pandas!

This is a tricky one. In the beginning we wanted people to come from pandas to xarray. It was kind of assumed that everybody uses and loves pandas, therefore will also use and love xarray. (my own experience).

But do we have to build the docs for non-pandas users as well? It could make quite a few things redundant with the pandas documentation...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   docs questions from new user 435330735

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