issue_comments

Table actions

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

  • drop zarr variable name from the dask chunk name · 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
366317495 https://github.com/pydata/xarray/pull/1907#issuecomment-366317495 https://api.github.com/repos/pydata/xarray/issues/1907 MDEyOklzc3VlQ29tbWVudDM2NjMxNzQ5NQ== jhamman 2443309 2018-02-16T18:22:59Z 2018-02-16T18:22:59Z MEMBER

I thought about this when I was making the change. I also don't think it requires a test. Obviously we weren't testing this before and its really just a cosmetic change. If anyone else feels differently, I can certainly look into writing a simple test. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   drop zarr variable name from the dask chunk name 296847687

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