issue_comments
4 rows where author_association = "MEMBER", issue = 1261153511 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association, issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1154368202 | https://github.com/pydata/xarray/pull/6665#issuecomment-1154368202 | https://api.github.com/repos/pydata/xarray/issues/6665 | IC_kwDOAMm_X85EzkLK | max-sixty 5635139 | 2022-06-13T19:54:41Z | 2022-06-13T19:54:41Z | MEMBER | Yes great, let's merge this.
Then two main options I see for synthesizing the vars issues:
- |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Update DataArray.rename + docu 1261153511 | |
1152977928 | https://github.com/pydata/xarray/pull/6665#issuecomment-1152977928 | https://api.github.com/repos/pydata/xarray/issues/6665 | IC_kwDOAMm_X85EuQwI | max-sixty 5635139 | 2022-06-11T18:32:14Z | 2022-06-11T18:32:14Z | MEMBER | @keewis v interesting suggestion — the object name as positional and vars as kwargs. As I think was mentioned above, one choice is whether a kwarg with the name of the object renames the object. I would worry it's slightly ambiguous. And potentially not additive. WDYT?
This could be good. Would this also rename the coord associated with the dim? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Update DataArray.rename + docu 1261153511 | |
1150582510 | https://github.com/pydata/xarray/pull/6665#issuecomment-1150582510 | https://api.github.com/repos/pydata/xarray/issues/6665 | IC_kwDOAMm_X85ElH7u | max-sixty 5635139 | 2022-06-09T01:45:57Z | 2022-06-09T01:46:07Z | MEMBER |
We do want it to be fluent though, so it can be directly on the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Update DataArray.rename + docu 1261153511 | |
1150438146 | https://github.com/pydata/xarray/pull/6665#issuecomment-1150438146 | https://api.github.com/repos/pydata/xarray/issues/6665 | IC_kwDOAMm_X85EkksC | max-sixty 5635139 | 2022-06-08T21:35:33Z | 2022-06-08T21:35:33Z | MEMBER | This seems like a nice improvement given the existing state. I've found the effort to specialize methods (e.g. ...which is not ideal, though might be the best tradeoff. WDYT @headtr1ck ? Or any other thoughts from others? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Update DataArray.rename + docu 1261153511 |
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