issue_comments
3 rows where author_association = "MEMBER" and issue = 718716799 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Scalar non-dimension coords forget their heritage · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
708588777 | https://github.com/pydata/xarray/issues/4501#issuecomment-708588777 | https://api.github.com/repos/pydata/xarray/issues/4501 | MDEyOklzc3VlQ29tbWVudDcwODU4ODc3Nw== | shoyer 1217238 | 2020-10-14T18:41:21Z | 2020-10-14T18:41:32Z | MEMBER | If we changed There's a bit of a conflict here between two desirable properties:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Scalar non-dimension coords forget their heritage 718716799 | |
708167473 | https://github.com/pydata/xarray/issues/4501#issuecomment-708167473 | https://api.github.com/repos/pydata/xarray/issues/4501 | MDEyOklzc3VlQ29tbWVudDcwODE2NzQ3Mw== | shoyer 1217238 | 2020-10-14T05:33:59Z | 2020-10-14T05:33:59Z | MEMBER |
Thanks for clarifying! One problem with this -- at least for now -- is that xarray currently doesn't allow coordinates on DataArray objects to have dimensions that don't appear on the DataArray itself. It might also be surprising that this would make |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Scalar non-dimension coords forget their heritage 718716799 | |
706639713 | https://github.com/pydata/xarray/issues/4501#issuecomment-706639713 | https://api.github.com/repos/pydata/xarray/issues/4501 | MDEyOklzc3VlQ29tbWVudDcwNjYzOTcxMw== | shoyer 1217238 | 2020-10-11T02:26:42Z | 2020-10-11T02:26:42Z | MEMBER | Hi @chrisroat, thanks for the clear bug report! It indeed be nice if For example, this array does currently satisfy your desired property, but wouldn't if we made the change you request:
I suspect our best option for achieving this behavior would be to add another optional argument to |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Scalar non-dimension coords forget their heritage 718716799 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1