issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 294089233 and user = 1217238 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

  • shoyer · 2 ✖

issue 1

  • Raise when pcolormesh coordinate is not sorted · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
366538974 https://github.com/pydata/xarray/pull/1885#issuecomment-366538974 https://api.github.com/repos/pydata/xarray/issues/1885 MDEyOklzc3VlQ29tbWVudDM2NjUzODk3NA== shoyer 1217238 2018-02-18T19:06:36Z 2018-02-18T19:06:36Z MEMBER

Thanks @nbren12 !

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Raise when pcolormesh coordinate is not sorted 294089233
362991345 https://github.com/pydata/xarray/pull/1885#issuecomment-362991345 https://api.github.com/repos/pydata/xarray/issues/1885 MDEyOklzc3VlQ29tbWVudDM2Mjk5MTM0NQ== shoyer 1217238 2018-02-05T06:15:12Z 2018-02-05T06:15:12Z MEMBER

Is there any chance people would want to make heatmaps involving categorical variables though?

Certainly, but the currently version of 2D plots in xarray doesn't work for these!

If they want to make plots involving categorical variables, I would currently recommend using seaborn.heatmap (we can mention it in the error message, too).

If we do decide to raise an error, why not go one step further and just sort the coordinates automatically?

One reason is that it's not obvious if they would like increasing or decreasing coordinates.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Raise when pcolormesh coordinate is not sorted 294089233

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