issue_comments

Table actions

1 row where issue = 1124596666 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

  • [API]: inconsistent `rename` for DataArray vs Dataset · 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
1039990176 https://github.com/pydata/xarray/issues/6238#issuecomment-1039990176 https://api.github.com/repos/pydata/xarray/issues/6238 IC_kwDOAMm_X849_P2g benbovy 4160723 2022-02-15T08:24:58Z 2022-02-15T08:24:58Z MEMBER

This is indeed confusing. Both Dataset.rename and DataArray.rename do a bit too much, IMHO.

For Dataset, I actually prefer using rename_dims or rename_vars as it is easier to understand.

Maybe we could add similar methods for DataArray too, e.g., rename_dims and rename_coords? And also rename_array?

To go even further, should we eventually depreciate the generic rename methods and encourage using the more specific methods? 

{
    "total_count": 6,
    "+1": 6,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [API]: inconsistent `rename` for DataArray vs Dataset 1124596666

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