issue_comments
3 rows where author_association = "CONTRIBUTOR" and issue = 499807676 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Add glossary to documentation · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
536352264 | https://github.com/pydata/xarray/pull/3352#issuecomment-536352264 | https://api.github.com/repos/pydata/xarray/issues/3352 | MDEyOklzc3VlQ29tbWVudDUzNjM1MjI2NA== | gwgundersen 2818208 | 2019-09-29T23:34:32Z | 2019-09-29T23:34:32Z | CONTRIBUTOR | I've integrated the latest feedback and created https://github.com/pydata/xarray/issues/3356 for the section on name-matching rules. @jthielen, it's not my call, but I think a downstream PR makes sense. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add glossary to documentation 499807676 | |
536350457 | https://github.com/pydata/xarray/pull/3352#issuecomment-536350457 | https://api.github.com/repos/pydata/xarray/issues/3352 | MDEyOklzc3VlQ29tbWVudDUzNjM1MDQ1Nw== | jthielen 3460034 | 2019-09-29T23:05:46Z | 2019-09-29T23:05:46Z | CONTRIBUTOR | Since the current wording of the "Coordinate" definition seems to imply only one dimension, should the multidimensional coordinate issue that remains be cleared up here or in a follow-up PR? If it's a follow-up, I'd be glad to submit one for it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add glossary to documentation 499807676 | |
536317258 | https://github.com/pydata/xarray/pull/3352#issuecomment-536317258 | https://api.github.com/repos/pydata/xarray/issues/3352 | MDEyOklzc3VlQ29tbWVudDUzNjMxNzI1OA== | gwgundersen 2818208 | 2019-09-29T16:18:11Z | 2019-09-29T16:18:11Z | CONTRIBUTOR | Thanks for the feedback @max-sixty and @dcherian. I tried to incorporate your feedback and pushed some new changes. Here's a screenshot of the page. Happy to iterate more on this if needed. I do think getting this stuff right is really useful for new users.
Ah, these would be great to have. I've created https://github.com/pydata/xarray/issues/3355 so I/we remember. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add glossary to documentation 499807676 |
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