issue_comments
3 rows where issue = 1385143758 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Fix `utils.get_axis` with kwargs · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1259952702 | https://github.com/pydata/xarray/pull/7080#issuecomment-1259952702 | https://api.github.com/repos/pydata/xarray/issues/7080 | IC_kwDOAMm_X85LGVo- | headtr1ck 43316012 | 2022-09-27T19:26:29Z | 2022-09-27T19:26:29Z | COLLABORATOR | And additionaly, we should change the description. The one of Thanks for noticing! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Fix `utils.get_axis` with kwargs 1385143758 | |
| 1259931046 | https://github.com/pydata/xarray/pull/7080#issuecomment-1259931046 | https://api.github.com/repos/pydata/xarray/issues/7080 | IC_kwDOAMm_X85LGQWm | headtr1ck 43316012 | 2022-09-27T19:04:42Z | 2022-09-27T19:04:42Z | COLLABORATOR |
If you do not specify size, figsize, aspect, row, col or ax, it should still use the current axis. But you are right, that deserves a test :) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Fix `utils.get_axis` with kwargs 1385143758 | |
| 1259913775 | https://github.com/pydata/xarray/pull/7080#issuecomment-1259913775 | https://api.github.com/repos/pydata/xarray/issues/7080 | IC_kwDOAMm_X85LGMIv | DWesl 22566757 | 2022-09-27T18:47:00Z | 2022-09-27T18:47:00Z | CONTRIBUTOR | I think the current default for two-dimensional plots is to try to re-use an existing axis if neither |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Fix `utils.get_axis` with kwargs 1385143758 |
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 2