issue_comments

Table actions

1 row where issue = 1028110240 and user = 31640292 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • WardBrian · 1 ✖

issue 1

  • Generator for groupby reductions · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
958130347 https://github.com/pydata/xarray/pull/5871#issuecomment-958130347 https://api.github.com/repos/pydata/xarray/issues/5871 IC_kwDOAMm_X845G-ir WardBrian 31640292 2021-11-02T20:11:23Z 2021-11-02T20:11:23Z CONTRIBUTOR

the new |-operator

from __future__ import annotations does not actually directly enable the use of | for union, it changes the semantics of type annotations to postpone evaluation. In particular, you can then put just about anything in the type annotation without having any runtime behavior:

python from __future__ import annotations def foo(bar: print('hi')) -> None: pass

This is separate from PEP 604 which actually does change the syntax.

Tools like mypy will catch obvious errors like the above, and support | if they are versioned sufficiently, but it's probably not a good idea to change unless you're certain that postponing evaluation is correct (Python itself has delayed making this the default to resolve some other issues). 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generator for groupby reductions 1028110240

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);