issue_comments
2 rows where author_association = "MEMBER" and issue = 842436143 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Lazy indexing arrays as a stand-alone package · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1414187606 | https://github.com/pydata/xarray/issues/5081#issuecomment-1414187606 | https://api.github.com/repos/pydata/xarray/issues/5081 | IC_kwDOAMm_X85USspW | Illviljan 14371165 | 2023-02-02T18:32:23Z | 2023-02-02T18:32:23Z | MEMBER | It is recommended to use it for lazy backends though: https://docs.xarray.dev/en/stable/internals/how-to-add-new-backend.html#how-to-support-lazy-loading |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Lazy indexing arrays as a stand-alone package 842436143 | |
1414068565 | https://github.com/pydata/xarray/issues/5081#issuecomment-1414068565 | https://api.github.com/repos/pydata/xarray/issues/5081 | IC_kwDOAMm_X85USPlV | shoyer 1217238 | 2023-02-02T17:00:39Z | 2023-02-02T17:00:39Z | MEMBER | Is Personally I would not want to guarantee external stability/availability for this API in its current state. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Lazy indexing arrays as a stand-alone package 842436143 |
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