issue_comments

Table actions

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

  • dcherian · 1 ✖

issue 1

  • Convert Variable to IndexVariable or vice versa when renamed · 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
762894414 https://github.com/pydata/xarray/pull/4108#issuecomment-762894414 https://api.github.com/repos/pydata/xarray/issues/4108 MDEyOklzc3VlQ29tbWVudDc2Mjg5NDQxNA== dcherian 2448579 2021-01-19T14:56:22Z 2021-01-19T14:57:45Z MEMBER

I wonder if it would be better to first "reorganize" all of the existing functions

I fully agree. However the bug in #4107 is that an invalid xarray object is created (_assert_internal_invariants fails), so I think we should merge a solution even before cleaning up the API.

EDIT: @keewis shall we copy your comment to a new issue?

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Convert Variable to IndexVariable or vice versa when renamed 626625818

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