issue_comments
3 rows where author_association = "MEMBER", issue = 807764700 and user = 10194086 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- add typing to unary and binary arithmetic operators · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 789898568 | https://github.com/pydata/xarray/pull/4904#issuecomment-789898568 | https://api.github.com/repos/pydata/xarray/issues/4904 | MDEyOklzc3VlQ29tbWVudDc4OTg5ODU2OA== | mathause 10194086 | 2021-03-03T17:13:08Z | 2021-03-03T17:13:08Z | MEMBER | Just FYI #4881 and #4878 are done |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
add typing to unary and binary arithmetic operators 807764700 | |
| 779710237 | https://github.com/pydata/xarray/pull/4904#issuecomment-779710237 | https://api.github.com/repos/pydata/xarray/issues/4904 | MDEyOklzc3VlQ29tbWVudDc3OTcxMDIzNw== | mathause 10194086 | 2021-02-16T09:37:55Z | 2021-02-16T09:37:55Z | MEMBER | Thanks for your thought-out answer. That all sounds good to me.
So that works now? I remember vaguely that @max-sixty (?) had an issue with this pattern once.
I vote for
Yes, I think that's a problem of the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
add typing to unary and binary arithmetic operators 807764700 | |
| 778842603 | https://github.com/pydata/xarray/pull/4904#issuecomment-778842603 | https://api.github.com/repos/pydata/xarray/issues/4904 | MDEyOklzc3VlQ29tbWVudDc3ODg0MjYwMw== | mathause 10194086 | 2021-02-14T21:12:02Z | 2021-02-14T21:12:02Z | MEMBER | Thanks for the PR & your work. I'll need some time to digest that all... One thing I certainly would like to fix before merging this is #4881 (and merge #4878). I'd also be interested in your motivation for the stub files. (It's just that we don't have any of these so far). I am sure you saw this comment: so there would be an argument to create mixin-classes*. Another motivation would be that currently (with the * Well I just realised that your stub files are kind of mixin classes...
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
add typing to unary and binary arithmetic operators 807764700 |
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