issue_comments
1 row where issue = 977149831 and user = 4160723 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Coordinates implicitly created when passing a DataArray as coord to Dataset constructor · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
904446262 | https://github.com/pydata/xarray/issues/5732#issuecomment-904446262 | https://api.github.com/repos/pydata/xarray/issues/5732 | IC_kwDOAMm_X8416ME2 | benbovy 4160723 | 2021-08-24T08:43:07Z | 2021-08-24T12:11:28Z | MEMBER | I think a similar concern applies to That said, I agree that taking into account the (indexed) coordinates of the DataArray are important for alignment. The example below makes perfect sense: ```python
I guess my concern is related to the (my?) slightly ambiguous view of the DataArray concept as a single array-like vs. a collection of data + coordinates. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Coordinates implicitly created when passing a DataArray as coord to Dataset constructor 977149831 |
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