issue_comments

Table actions

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

  • TomNicholas · 1 ✖

issue 1

  • Interpolation using non-dimension coordinates · 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
535475540 https://github.com/pydata/xarray/issues/3343#issuecomment-535475540 https://api.github.com/repos/pydata/xarray/issues/3343 MDEyOklzc3VlQ29tbWVudDUzNTQ3NTU0MA== TomNicholas 35968931 2019-09-26T12:15:44Z 2019-09-26T12:15:44Z MEMBER

This is an example of a general UI problem which I was actually about to raise an issue about.

There are loads of places in xarray's API which require a dimension, but the operation would make just as much sense if a 1D coordinate were supplied instead (as that uniquely specifies a dimension).

I encountered the same kind of problem in #3334 with da.transpose().

I wonder if it would be possible to have a little helper function process the dim input to these functions and if it's a 1D coord, just demote it to the corresponding dim. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Interpolation using non-dimension coordinates 498297720

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