issue_comments
4 rows where author_association = "MEMBER", issue = 352677925 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Make `dim` optional on unstack · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
415647225 | https://github.com/pydata/xarray/pull/2375#issuecomment-415647225 | https://api.github.com/repos/pydata/xarray/issues/2375 | MDEyOklzc3VlQ29tbWVudDQxNTY0NzIyNQ== | shoyer 1217238 | 2018-08-24T04:24:33Z | 2018-08-24T04:24:33Z | MEMBER | It might make sense to use a list instead of a set here. On Thu, Aug 23, 2018 at 8:37 PM Keisuke Fujii notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Make `dim` optional on unstack 352677925 | |
415492951 | https://github.com/pydata/xarray/pull/2375#issuecomment-415492951 | https://api.github.com/repos/pydata/xarray/issues/2375 | MDEyOklzc3VlQ29tbWVudDQxNTQ5Mjk1MQ== | shoyer 1217238 | 2018-08-23T17:01:23Z | 2018-08-23T17:01:23Z | MEMBER | Dataset.transpose accepts *args based on the design of numpy.ndarray.transpose, but that API is probably a mistake (both in NumPy and xarray). Everything else uses an axis/dim argument that can take a scalar or sequence value. On Thu, Aug 23, 2018 at 9:56 AM Julia Signell notifications@github.com wrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Make `dim` optional on unstack 352677925 | |
415486919 | https://github.com/pydata/xarray/pull/2375#issuecomment-415486919 | https://api.github.com/repos/pydata/xarray/issues/2375 | MDEyOklzc3VlQ29tbWVudDQxNTQ4NjkxOQ== | shoyer 1217238 | 2018-08-23T16:46:41Z | 2018-08-23T16:46:41Z | MEMBER |
Usually we prefer to stick to a single argument, but use isinstance checks to support both single dimensions and lists of dimensions, e.g., see how |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Make `dim` optional on unstack 352677925 | |
415227870 | https://github.com/pydata/xarray/pull/2375#issuecomment-415227870 | https://api.github.com/repos/pydata/xarray/issues/2375 | MDEyOklzc3VlQ29tbWVudDQxNTIyNzg3MA== | shoyer 1217238 | 2018-08-23T00:06:56Z | 2018-08-23T00:06:56Z | MEMBER | I think
I'm not really opposed to Maybe we can figure a better way to spell "label these arrays like this template xarray object" that doesn't require referencing
I'm not sure that a dedicated function |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Make `dim` optional on unstack 352677925 |
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