issue_comments

Table actions

1 row where issue = 1423114234 and user = 39069044 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

  • slevang · 1 ✖

issue 1

  • `xr.where(..., keep_attrs=True)` overwrites coordinate attributes · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1291957109 https://github.com/pydata/xarray/issues/7220#issuecomment-1291957109 https://api.github.com/repos/pydata/xarray/issues/7220 IC_kwDOAMm_X85NAbN1 slevang 39069044 2022-10-26T12:26:55Z 2022-10-26T12:26:55Z CONTRIBUTOR

Anything that uses attrs[1] and the _get_all_of_type helper is going to be hard to guarantee the behavior stated in the docstring, which is that we take the attrs of x. If x is a scalar, then _get_all_of_type returns a list of length 2 and attrs[1] ends up being the attrs of y. I think we may want to rework this, will try a few things later today.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `xr.where(..., keep_attrs=True)` overwrites coordinate attributes 1423114234

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