issue_comments

Table actions

1 row where issue = 937336962 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • keewis · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
875091663 https://github.com/pydata/xarray/pull/5580#issuecomment-875091663 https://api.github.com/repos/pydata/xarray/issues/5580 MDEyOklzc3VlQ29tbWVudDg3NTA5MTY2Mw== keewis 14808389 2021-07-06T21:24:02Z 2021-07-06T21:24:02Z MEMBER

I also think we should be able to merge once the points @max-sixty mentioned have been addressed, but if you feel uncomfortable with merging now we can wait until after the next release (which should be soon, given that we have a compatibility issue with pandas=1.3).

The changelog is in /doc/whats-new.rst, and the reprs are documented in /doc/user-guide/data-structures.rst (not sure if that has to be modified), but there might be other files / docstrings.

For tests we usually use pytest.mark.parametrize. This would require a new test function (test_display_max_rows?), where you could check the number of lines of the repr.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   dataset `__repr__` updates 937336962

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