issue_comments
1 row where issue = 806811808 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- support passing a function to combine_attrs · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
849236342 | https://github.com/pydata/xarray/pull/4896#issuecomment-849236342 | https://api.github.com/repos/pydata/xarray/issues/4896 | MDEyOklzc3VlQ29tbWVudDg0OTIzNjM0Mg== | shoyer 1217238 | 2021-05-27T01:08:10Z | 2021-05-27T01:08:10Z | MEMBER |
Rather than introspection, I think we should try to be fully explicit about the function being called. Trying to introspect it from stack-frames is madness :) So in that case, we would need to pass down the context information from the top level functions in xarray, e.g., everything that takes a In terms of the overall interface, one other concern I have is about the information we make available to users of this API. I can imagine that they might not only want attributes but also the complete xarray objects on which the function is being called. If that's the case, then they would also need more information from the global context. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
support passing a function to combine_attrs 806811808 |
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