issue_comments

Table actions

1 row where issue = 783630055 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • More advanced tutorial on how to manipulate facetgrid · 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
758249456 https://github.com/pydata/xarray/issues/4793#issuecomment-758249456 https://api.github.com/repos/pydata/xarray/issues/4793 MDEyOklzc3VlQ29tbWVudDc1ODI0OTQ1Ng== shoyer 1217238 2021-01-11T21:54:47Z 2021-01-11T21:54:47Z MEMBER

I agree, I would love for facetting to be more easily extended! Documenting what already works is clearly the first step :)

As it, I must admit that although I use FaceGrid for exploratory visualization, I usually end up re-creating facets manually for publications.

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 1,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   More advanced tutorial on how to manipulate facetgrid 783630055

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