issue_comments
2 rows where author_association = "MEMBER", issue = 592312709 and user = 4160723 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- sel along 1D non-index coordinates · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 925694605 | https://github.com/pydata/xarray/pull/3925#issuecomment-925694605 | https://api.github.com/repos/pydata/xarray/issues/3925 | IC_kwDOAMm_X843LPqN | benbovy 4160723 | 2021-09-23T10:37:07Z | 2021-09-23T10:37:07Z | MEMBER | In #5692 it is possible to perform selection using non-dimension coordinates with an index, although there's no easy way yet to set an index for such coordinates (this will be done in a follow-up PR by updating the API of |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
sel along 1D non-index coordinates 592312709 | |
| 794116358 | https://github.com/pydata/xarray/pull/3925#issuecomment-794116358 | https://api.github.com/repos/pydata/xarray/issues/3925 | MDEyOklzc3VlQ29tbWVudDc5NDExNjM1OA== | benbovy 4160723 | 2021-03-09T16:23:17Z | 2021-03-09T16:23:17Z | MEMBER |
I think it's a good use case for some kind of |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
sel along 1D non-index coordinates 592312709 |
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