issue_comments
where issue = 216799807 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
These facets timed out: author_association, issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
289559455 | https://github.com/pydata/xarray/issues/1326#issuecomment-289559455 | https://api.github.com/repos/pydata/xarray/issues/1326 | MDEyOklzc3VlQ29tbWVudDI4OTU1OTQ1NQ== | shoyer 1217238 | 2017-03-27T19:28:36Z | 2017-03-27T19:28:36Z | MEMBER | One thing to make sure is if |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Expand dimensions in xarray 216799807 | |
289520057 | https://github.com/pydata/xarray/issues/1326#issuecomment-289520057 | https://api.github.com/repos/pydata/xarray/issues/1326 | MDEyOklzc3VlQ29tbWVudDI4OTUyMDA1Nw== | shoyer 1217238 | 2017-03-27T17:12:45Z | 2017-03-27T17:12:45Z | MEMBER | Looks good to me. I would just make the default |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Expand dimensions in xarray 216799807 | |
289513566 | https://github.com/pydata/xarray/issues/1326#issuecomment-289513566 | https://api.github.com/repos/pydata/xarray/issues/1326 | MDEyOklzc3VlQ29tbWVudDI4OTUxMzU2Ng== | shoyer 1217238 | 2017-03-27T16:50:02Z | 2017-03-27T16:50:02Z | MEMBER |
Yes, I think this would be too confusing. Function arguments should do one thing. What would
I think we could clarify this is by saying that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Expand dimensions in xarray 216799807 | |
289497437 | https://github.com/pydata/xarray/issues/1326#issuecomment-289497437 | https://api.github.com/repos/pydata/xarray/issues/1326 | MDEyOklzc3VlQ29tbWVudDI4OTQ5NzQzNw== | shoyer 1217238 | 2017-03-27T15:54:18Z | 2017-03-27T15:54:18Z | MEMBER | @fujiisoup I like your proposed API, but I would switch the order of the method arguments. That way, users who don't care about axis position can use a positional argument. We might also consider supporting inserting multiple axes at once, e.g., by passing a list/tuple to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Expand dimensions in xarray 216799807 | |
289084136 | https://github.com/pydata/xarray/issues/1326#issuecomment-289084136 | https://api.github.com/repos/pydata/xarray/issues/1326 | MDEyOklzc3VlQ29tbWVudDI4OTA4NDEzNg== | shoyer 1217238 | 2017-03-24T17:10:19Z | 2017-03-24T17:10:19Z | MEMBER | Can you propose what the API should look like? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Expand dimensions in xarray 216799807 |
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