issue_comments

Table actions

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

  • max-sixty · 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
609556676 https://github.com/pydata/xarray/issues/3939#issuecomment-609556676 https://api.github.com/repos/pydata/xarray/issues/3939 MDEyOklzc3VlQ29tbWVudDYwOTU1NjY3Ng== max-sixty 5635139 2020-04-06T04:20:23Z 2020-04-06T04:31:05Z MEMBER

Thanks for the suggestion @TomNicholas

I’d be -0.5 on this; it’s unpythonic given it’s not a call, and I do think it’s generally worth being consistent with the wider language.

There may also be functions that check whether arguments are callable (where / assign) that would break.

I also think our current solution of .sel is pretty good. If there’s demand for .loc(x=2), that would less intrusive than on the main object. 

{
    "total_count": 3,
    "+1": 3,
    "-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]);