issue_comments
2 rows where issue = 110820316 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- Don't squeeze DataArray before plotting · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 881582747 | https://github.com/pydata/xarray/issues/620#issuecomment-881582747 | https://api.github.com/repos/pydata/xarray/issues/620 | IC_kwDOAMm_X840i-Kb | shoyer 1217238 | 2021-07-16T16:48:59Z | 2021-07-16T16:48:59Z | MEMBER | I would support a breaking change to Xarray's plotting methods here to remove squeezing. These sort of inconsistencies are really indeed annoying to program around! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Don't squeeze DataArray before plotting 110820316 | |
| 147133468 | https://github.com/pydata/xarray/issues/620#issuecomment-147133468 | https://api.github.com/repos/pydata/xarray/issues/620 | MDEyOklzc3VlQ29tbWVudDE0NzEzMzQ2OA== | shoyer 1217238 | 2015-10-10T23:02:03Z | 2015-10-10T23:02:03Z | MEMBER | I see two options:
1. Squeeze after the 1 might actually be preferable to not squeezing at all. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Don't squeeze DataArray before plotting 110820316 |
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