issue_comments

Table actions

1 row where issue = 1244833334 and user = 43316012 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

  • headtr1ck · 1 ✖

issue 1

  • `{full,zeros,ones}_like` should return objects with the same type as the input object · 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
1134532080 https://github.com/pydata/xarray/issues/6628#issuecomment-1134532080 https://api.github.com/repos/pydata/xarray/issues/6628 IC_kwDOAMm_X85Dn5Xw headtr1ck 43316012 2022-05-23T11:06:46Z 2022-05-23T11:06:46Z COLLABORATOR

Nice find. Was a bug in the overloads, the PR should fix it.

If the bound TypeVar support of mypy would not be so buggy we could move to a simpler solution that is less error prone...

 
{
    "total_count": 2,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 1,
    "eyes": 0
}
   `{full,zeros,ones}_like` should return objects with the same type as the input object 1244833334

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