issue_comments

Table actions

1 row where issue = 116349205 and user = 2443309 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

  • jhamman · 1 ✖

issue 1

  • More control on cmap params · 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
155882953 https://github.com/pydata/xarray/pull/655#issuecomment-155882953 https://api.github.com/repos/pydata/xarray/issues/655 MDEyOklzc3VlQ29tbWVudDE1NTg4Mjk1Mw== jhamman 2443309 2015-11-11T19:16:20Z 2015-11-11T19:16:20Z MEMBER

I'll just chime in here quickly and layout how I think this should go - 1. If you set anything, it should not be overwritten. This includes the colormap and vmin/vmax. 2. If you want very specific/consistent behavior, you'll need to explicitly provide those arguments. 3. The only safe times to assume a diverging colormap is when vmin = -vmax or when center is not None. If you want a diverging colormap for other situations, you need to specify cmap in the plot call.

All in all, I think what I'm getting at is we may want to tighten up on when we switch from the default cmap to the diverging cmap.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More control on cmap params 116349205

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