issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 594688816 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 · 1 ✖

issue 1

  • Why don't we allow indexing with keyword args via __call__? · 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
611322614 https://github.com/pydata/xarray/issues/3939#issuecomment-611322614 https://api.github.com/repos/pydata/xarray/issues/3939 MDEyOklzc3VlQ29tbWVudDYxMTMyMjYxNA== shoyer 1217238 2020-04-09T04:33:41Z 2020-04-09T04:33:41Z MEMBER

I'm pretty happy with the .sel() API. One major advantage over using __call__ is that you can Google search for something like "xarray sel" and get sensible results.

The main downside is that you can't use it for assignment, but that wouldn't be solved by overriding __call__ either.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Why don't we allow indexing with keyword args via __call__? 594688816

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