issue_comments

Table actions

where author_association = "MEMBER", issue = 679575175 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association

user 1

  • shoyer · 1 ✖

issue 1

  • Improve Dataset documentation · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
675234132 https://github.com/pydata/xarray/issues/4345#issuecomment-675234132 https://api.github.com/repos/pydata/xarray/issues/4345 MDEyOklzc3VlQ29tbWVudDY3NTIzNDEzMg== shoyer 1217238 2020-08-18T03:54:57Z 2020-08-18T03:54:57Z MEMBER

I don't think it's unusual to document constructor parameters on __init__. For example, that's the recommendation of the Google Python style-guide, followed by most Google Python projects (e.g., TensorFlow). So I think Spyder would be improved by documenting __init__, too.

That said, I don't have any principled reason for deviating from the NumPy docstring standards here. I also agree that the Dataset constructor would be improved by adding usage examples of how to create a Dataset.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Improve Dataset documentation 679575175

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