issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 337202341 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • fmaussion · 2 ✖

issue 1

  • Plotting: do not check for monotonicity with 2D coords · 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
402070480 https://github.com/pydata/xarray/pull/2260#issuecomment-402070480 https://api.github.com/repos/pydata/xarray/issues/2260 MDEyOklzc3VlQ29tbWVudDQwMjA3MDQ4MA== fmaussion 10050469 2018-07-03T09:17:02Z 2018-07-03T09:17:02Z MEMBER

What will happen if the coordinate is a MultiIndex ? I often encounter this issue and am insisted to drop the coordinate manually. If it automatically drops the MultiIndex for plotting, that would be nicer.

@fujiisoup can you open a separate issue for this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Plotting: do not check for monotonicity with 2D coords 337202341
401530507 https://github.com/pydata/xarray/pull/2260#issuecomment-401530507 https://api.github.com/repos/pydata/xarray/issues/2260 MDEyOklzc3VlQ29tbWVudDQwMTUzMDUwNw== fmaussion 10050469 2018-06-30T09:48:39Z 2018-06-30T09:48:39Z MEMBER

As shown in https://github.com/pydata/xarray/issues/2250 , 2D coords with non-monotonic coordinates are perfectly valid and well handled by xarray's coordinate checks.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Plotting: do not check for monotonicity with 2D coords 337202341

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