issue_comments

Table actions

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

  • Should __repr__ and __str__ be PEP8 compliant? · 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
678722063 https://github.com/pydata/xarray/issues/4367#issuecomment-678722063 https://api.github.com/repos/pydata/xarray/issues/4367 MDEyOklzc3VlQ29tbWVudDY3ODcyMjA2Mw== shoyer 1217238 2020-08-23T02:54:04Z 2020-08-23T02:54:04Z MEMBER

Our default line width limit for text repr() is actually already 80 characters. This matches display.width from pandas, and is a little longer than what NumPy uses (75 characters).

You can definitely set a lower line width if you like for rendering repr() when copying and pasting into docstrings, using xarray.set_options.

I don't think we should change this overall, because copying and pasting into docstring is a relatively rare use of repr() compared to printing data in a console.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Should __repr__ and __str__ be PEP8 compliant? 683954433

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