issue_comments
2 rows where author_association = "MEMBER" and issue = 856900805 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Handling of non-string dimension names · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
818809386 | https://github.com/pydata/xarray/issues/5148#issuecomment-818809386 | https://api.github.com/repos/pydata/xarray/issues/5148 | MDEyOklzc3VlQ29tbWVudDgxODgwOTM4Ng== | keewis 14808389 | 2021-04-13T15:05:02Z | 2021-04-13T15:05:43Z | MEMBER |
I think improving the error message is the way to go.
I think we can keep the discussion here |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handling of non-string dimension names 856900805 | |
818734171 | https://github.com/pydata/xarray/issues/5148#issuecomment-818734171 | https://api.github.com/repos/pydata/xarray/issues/5148 | MDEyOklzc3VlQ29tbWVudDgxODczNDE3MQ== | keewis 14808389 | 2021-04-13T13:25:54Z | 2021-04-13T13:29:27Z | MEMBER | we do want to allow general hashables to mirror the general |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handling of non-string dimension names 856900805 |
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