issue_comments

Table actions

1 row where issue = 400289716 and user = 5635139 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

  • max-sixty · 1 ✖

issue 1

  • Is `create_test_data()` public API? · 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
455208128 https://github.com/pydata/xarray/issues/2686#issuecomment-455208128 https://api.github.com/repos/pydata/xarray/issues/2686 MDEyOklzc3VlQ29tbWVudDQ1NTIwODEyOA== max-sixty 5635139 2019-01-17T15:17:02Z 2019-01-17T15:17:02Z MEMBER

I think we could make that public, interested in others' thoughts

I'm often creating my own ds manually, and should instead just call that to get an object.

We could also promote it to xarray.testing if that make it more accessible and the API more explicit. And potentially encourage its usage in tests rather than manually creating a ds fixture. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Is `create_test_data()` public API? 400289716

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