issue_comments

Table actions

1 row where author_association = "NONE" and issue = 765639913 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

issue 1

  • keep attrs in xarray.where · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
920104073 https://github.com/pydata/xarray/pull/4687#issuecomment-920104073 https://api.github.com/repos/pydata/xarray/issues/4687 IC_kwDOAMm_X84216yJ rjlauer 10870503 2021-09-15T15:05:46Z 2021-09-15T15:05:46Z NONE

Hi, I have a question about this fix relating to coordinate attributes (and am not sure if that deserves a separate issue): In xarray version 0.17.0, coordinate attributes are being preserved when using xr.where. But, in version 0.19.0, that is not the case anymore. Does the solution for preserving DataArray attributes as discussed here also solve (or rather re-enable) preservation of coordinate attributes? It looks like DataArray.where still preserves coordinate attributes even in version 0.19.0, so I would hope the answer is yes?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   keep attrs in xarray.where 765639913

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