issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 198030158 and user = 5356122 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

  • clarkfitzg · 1 ✖

issue 1

  • Integer levels and vmin/vmax · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
269819094 https://github.com/pydata/xarray/pull/1191#issuecomment-269819094 https://api.github.com/repos/pydata/xarray/issues/1191 MDEyOklzc3VlQ29tbWVudDI2OTgxOTA5NA== clarkfitzg 5356122 2016-12-30T20:36:44Z 2016-12-30T20:37:02Z MEMBER

It is consistent with mpl, as long as neither vmin or vmax are set.

The reason for having consistency with MPL is that users can take essentially the same code and produce the same plots with or without xarray. And it's less work on this end.

We're departing from that here to get something that perhaps is more natural for the user. But I think it's ok since the plots generally won't look all that different. If users want more control they can just set all the levels explicitly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Integer levels and vmin/vmax 198030158

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