issue_comments

Table actions

2 rows where issue = 789106802 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • max-sixty · 2 ✖

issue 1

  • clean up the API for renaming and changing dimensions / coordinates · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
766429379 https://github.com/pydata/xarray/issues/4825#issuecomment-766429379 https://api.github.com/repos/pydata/xarray/issues/4825 MDEyOklzc3VlQ29tbWVudDc2NjQyOTM3OQ== max-sixty 5635139 2021-01-24T20:48:19Z 2021-01-24T20:48:19Z MEMBER

There's also rename_dims, but only on a Dataset! There's a TODO to deprecate swap_dims in favor of that. Though I'm not sure that's right — swap_dims changes the dim values for another variable's, but rename_dims just changes the name?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   clean up the API for renaming and changing dimensions / coordinates 789106802
763219168 https://github.com/pydata/xarray/issues/4825#issuecomment-763219168 https://api.github.com/repos/pydata/xarray/issues/4825 MDEyOklzc3VlQ29tbWVudDc2MzIxOTE2OA== max-sixty 5635139 2021-01-19T23:53:34Z 2021-01-19T23:53:34Z MEMBER

I agree it's confusing, and I find myself looking up the correct way to do something fairly frequently.

I'm not sure exactly how to rationalize them though.

Without thinking this through in enough detail, Does set_ set the variable to the relevant type and reset_ unsets it to a normal variable? In that framework, I think the only aberrant is swap_dims, which could instead be set_dims?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   clean up the API for renaming and changing dimensions / coordinates 789106802

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