issue_comments
2 rows where author_association = "MEMBER", issue = 715374721 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Group together decoding options into a single argument · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
704631854 | https://github.com/pydata/xarray/issues/4490#issuecomment-704631854 | https://api.github.com/repos/pydata/xarray/issues/4490 | MDEyOklzc3VlQ29tbWVudDcwNDYzMTg1NA== | shoyer 1217238 | 2020-10-07T01:02:41Z | 2020-10-07T01:02:41Z | MEMBER | I see this as complementary to @alexamici's proposal in https://github.com/pydata/xarray/issues/4309#issuecomment-697952300, which I also like. I guess the main difference is moving Auto-completion is one reason to prefer a class, but enforced error checking and consistency between backends in the data model are also good reasons. In particular, it is important that users get an error if they mis-spell an argument name, e.g., I guess cfgrib is an example of a backend with its own CF decoding options? This is indeed a tricky design question. I don't know if it's possible to make |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Group together decoding options into a single argument 715374721 | |
704396229 | https://github.com/pydata/xarray/issues/4490#issuecomment-704396229 | https://api.github.com/repos/pydata/xarray/issues/4490 | MDEyOklzc3VlQ29tbWVudDcwNDM5NjIyOQ== | shoyer 1217238 | 2020-10-06T16:25:54Z | 2020-10-06T16:25:54Z | MEMBER |
works for me! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Group together decoding options into a single argument 715374721 |
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