issue_comments

Table actions

2 rows where issue = 32928338 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

  • Allow DataArray objects without named dimensions? · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
48102231 https://github.com/pydata/xarray/issues/116#issuecomment-48102231 https://api.github.com/repos/pydata/xarray/issues/116 MDEyOklzc3VlQ29tbWVudDQ4MTAyMjMx shoyer 1217238 2014-07-06T03:38:48Z 2014-07-06T03:38:48Z MEMBER

Closing this as "won't fix"

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow DataArray objects without named dimensions? 32928338
42633675 https://github.com/pydata/xarray/issues/116#issuecomment-42633675 https://api.github.com/repos/pydata/xarray/issues/116 MDEyOklzc3VlQ29tbWVudDQyNjMzNjc1 shoyer 1217238 2014-05-09T05:01:38Z 2014-05-09T05:02:16Z MEMBER

As I think more about this one, I'm questioning the value of allowing for unnamed dimensions, as opposed to simply defaulting to dimension names like "dim_0", "dim_1", etc.

In particular, unnamed dimensions are not very useful on object which use indices for alignment. To do sensible numpy like broadcasting, you need to be able to insert size 1 dimensions. But since we always have tick labels, we can't automatically expand those size 1 dimensions to the size of the dimension in the other array.

I suppose we could also make tick labels optional, which would make reshape operations or np.newaxis sensible. But I think I would rather still default to np.arange(size) like pandas.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow DataArray objects without named dimensions? 32928338

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