issue_comments

Table actions

3 rows where issue = 377356113 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • full_like, ones_like, zeros_like should retain subclasses · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1453094468 https://github.com/pydata/xarray/issues/2542#issuecomment-1453094468 https://api.github.com/repos/pydata/xarray/issues/2542 IC_kwDOAMm_X85WnHZE TomNicholas 35968931 2023-03-03T07:27:48Z 2023-03-03T07:27:48Z MEMBER

See #3980 - this issue should be solved as part of #3980, but see that issue for more general discussion of subclassing.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   full_like, ones_like, zeros_like should retain subclasses 377356113
706795159 https://github.com/pydata/xarray/issues/2542#issuecomment-706795159 https://api.github.com/repos/pydata/xarray/issues/2542 MDEyOklzc3VlQ29tbWVudDcwNjc5NTE1OQ== stale[bot] 26384082 2020-10-12T00:30:43Z 2020-10-12T00:30:43Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   full_like, ones_like, zeros_like should retain subclasses 377356113
436279947 https://github.com/pydata/xarray/issues/2542#issuecomment-436279947 https://api.github.com/repos/pydata/xarray/issues/2542 MDEyOklzc3VlQ29tbWVudDQzNjI3OTk0Nw== shoyer 1217238 2018-11-06T14:53:11Z 2018-11-06T14:53:11Z MEMBER

Are there other functions where we don't do this?

I would be happy to accept a fix here. I don't think we need a few keyword argument -- I expect most subclass users would consider this a bug rather than a feature.

We might consider adding an official subclassing APIs like pandas: https://pandas.pydata.org/pandas-docs/stable/extending.html#extending-subclassing-pandas

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   full_like, ones_like, zeros_like should retain subclasses 377356113

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