issue_comments

Table actions

1 row where issue = 1091822549 and user = 1562854 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

  • jklymak · 1 ✖

issue 1

  • TST: check datetime converter is Matplotlibs · 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
1003582857 https://github.com/pydata/xarray/pull/6128#issuecomment-1003582857 https://api.github.com/repos/pydata/xarray/issues/6128 IC_kwDOAMm_X8470XWJ jklymak 1562854 2022-01-01T16:45:01Z 2022-01-01T16:45:01Z CONTRIBUTOR

The point of my original concern was the case where the automatic import should not nbe happening. I think that the new version of my test should work with the revert of #6109.

I agree that the import logic is a bit of a pain. OTOH I'm not sure how to make it better. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   TST: check datetime converter is Matplotlibs 1091822549

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