issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 291565176 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

issue 1

  • Time decoding has round-off error 0.10.0. Gone now. · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
360577853 https://github.com/pydata/xarray/issues/1859#issuecomment-360577853 https://api.github.com/repos/pydata/xarray/issues/1859 MDEyOklzc3VlQ29tbWVudDM2MDU3Nzg1Mw== shoyer 1217238 2018-01-25T19:42:59Z 2018-01-25T19:42:59Z MEMBER

Interesting. This definitely wasn't an intended fix, though, so it would probably still be a good idea to add a test-case covering this behavior so we don't have a regression (there are plans to refactor the encoding/decoding module more in the future). Any interesting in putting together a PR with a test?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time decoding has round-off error 0.10.0. Gone now. 291565176

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