issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 264082543 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

  • __array_ufunc__ for xarray · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
370276833 https://github.com/pydata/xarray/issues/1617#issuecomment-370276833 https://api.github.com/repos/pydata/xarray/issues/1617 MDEyOklzc3VlQ29tbWVudDM3MDI3NjgzMw== shoyer 1217238 2018-03-05T00:00:57Z 2018-03-05T00:00:57Z MEMBER

I'm starting to work on this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   __array_ufunc__ for xarray 264082543
340290288 https://github.com/pydata/xarray/issues/1617#issuecomment-340290288 https://api.github.com/repos/pydata/xarray/issues/1617 MDEyOklzc3VlQ29tbWVudDM0MDI5MDI4OA== shoyer 1217238 2017-10-29T20:09:12Z 2017-10-29T20:09:12Z MEMBER

A related task would be finishing up this PR:

  • 1118: Do not convert subclasses of ndarray unless required

Ultimately, it would be nice to have some sort of registration system, especially for objects that aren't ndarray subclasses, that indicates that a class can safely be wrapped by xarray.

I'm thinking something like xarray.register_data_type(ArrayWithUnits) which indicates that .data for xarray objects can now be an ArrayWithUnits object. This would also possibly require passing a reference to a set of function to use on data containing these objects (e.g., for stacking or concatenating).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   __array_ufunc__ for xarray 264082543

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