issue_comments

Table actions

4 rows where author_association = "COLLABORATOR" and issue = 1452123685 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

issue 1

  • DataArray.transpose with transpose_coords=True does not change coords order · 4 ✖

author_association 1

  • COLLABORATOR · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1326809036 https://github.com/pydata/xarray/issues/7294#issuecomment-1326809036 https://api.github.com/repos/pydata/xarray/issues/7294 IC_kwDOAMm_X85PFX_M headtr1ck 43316012 2022-11-24T20:07:47Z 2022-11-24T20:07:47Z COLLABORATOR

Just noticed that the same logic does not work for Datasets, since all variables are kept in a common dict and the information about which are coordinates and which are data-variables is kept in a set, which is not ordered...

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray.transpose with transpose_coords=True does not change coords order 1452123685
1326804904 https://github.com/pydata/xarray/issues/7294#issuecomment-1326804904 https://api.github.com/repos/pydata/xarray/issues/7294 IC_kwDOAMm_X85PFW-o headtr1ck 43316012 2022-11-24T19:59:42Z 2022-11-24T19:59:42Z COLLABORATOR

The logic for this is not really trivial unless I am missing some obvious trick. You basically have to change the loop here: https://github.com/pydata/xarray/blob/ff6793d975ef4d1d8d5d32b8ad6f4f44e02dda9b/xarray/core/dataarray.py#L2919 To loop first over the new dims and potential coordinates with the same name and then over the rest of the coordinates (If possible in a single loop without code repetition).

Feel free to propose a PR!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray.transpose with transpose_coords=True does not change coords order 1452123685
1325699317 https://github.com/pydata/xarray/issues/7294#issuecomment-1325699317 https://api.github.com/repos/pydata/xarray/issues/7294 IC_kwDOAMm_X85PBJD1 headtr1ck 43316012 2022-11-23T21:48:28Z 2022-11-23T21:48:28Z COLLABORATOR

And what should happen with non-dimension coordinates? Should they simply end up in the end?

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray.transpose with transpose_coords=True does not change coords order 1452123685
1317531894 https://github.com/pydata/xarray/issues/7294#issuecomment-1317531894 https://api.github.com/repos/pydata/xarray/issues/7294 IC_kwDOAMm_X85Oh_D2 headtr1ck 43316012 2022-11-16T19:07:00Z 2022-11-16T19:07:13Z COLLABORATOR

The coordinates are just a mapping from names to DataArrays, I don't think the order has any meaning (like it does for normal dicts).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray.transpose with transpose_coords=True does not change coords order 1452123685

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