issue_comments

Table actions

3 rows where issue = 1275752720 and user = 5635139 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

  • max-sixty · 3 ✖

issue 1

  • Future of `DataArray.rename` · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1163311176 https://github.com/pydata/xarray/issues/6704#issuecomment-1163311176 https://api.github.com/repos/pydata/xarray/issues/6704 IC_kwDOAMm_X85FVrhI max-sixty 5635139 2022-06-22T16:06:13Z 2022-06-22T16:06:13Z MEMBER

As discussed on the call: - We'd like to move to .rename and .rename_vars as separate methods on DataArray; the latter renaming coords. - We would "soft-deprecate" .rename for renaming coords — i.e. remove documentation, but not give any warnings, at least for a while. This was a successful approach for .drop. - .rename_vars is a slightly odd name given there are only coords. But it's consistent with xr.Dataset.

After the call, I realize that I didn't mention that Dataset.rename is a synonym for Dataset.rename_vars. Would be also soft deprecate Dataset.rename?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Future of `DataArray.rename` 1275752720
1161952023 https://github.com/pydata/xarray/issues/6704#issuecomment-1161952023 https://api.github.com/repos/pydata/xarray/issues/6704 IC_kwDOAMm_X85FQfsX max-sixty 5635139 2022-06-21T15:59:22Z 2022-06-21T15:59:22Z MEMBER

I feel honored thanks! But given that I will become a father any day now, I don't think I will be able to join regularly...

Congrats on the forthcoming arrival!

Ofc, no stress if you can't make the meeting, and obv zero stress if you can't make lots of them.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Future of `DataArray.rename` 1275752720
1159784960 https://github.com/pydata/xarray/issues/6704#issuecomment-1159784960 https://api.github.com/repos/pydata/xarray/issues/6704 IC_kwDOAMm_X85FIOoA max-sixty 5635139 2022-06-19T18:00:50Z 2022-06-19T18:00:50Z MEMBER

This is the sort of thing we can discuss briefly on our dev call — which you would be more than welcome to attend and participate in @headtr1ck.

It's at 8.30AM PT every second Wednesday, including this coming Wednesday. I think there's an issue about it (though am on a plane wifi connection so currently difficult to search...). Unfortunately I've been poor at attendance recently given my schedule, but I have been trying to rearrange things so I can start attending again.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Future of `DataArray.rename` 1275752720

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