issue_comments

Table actions

1 row where issue = 1500636982 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

issue 1

  • Alternative, async-friendly pattern for `make_app_client()` and similar - fully retire `TestClient` · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1355691595 https://github.com/simonw/datasette/issues/1962#issuecomment-1355691595 https://api.github.com/repos/simonw/datasette/issues/1962 IC_kwDOBm6k_c5QzjZL simonw 9599 2022-12-16T21:53:45Z 2022-12-16T21:55:29Z OWNER

Also need an alternative mechanism to this convenience for getting CSRF tokens before a POST:

https://github.com/simonw/datasette/blob/5ee954e34b6eb762ccecbdb2be0791d0166fd19c/datasette/utils/testing.py#L90-L103

One option would be adding that mechanism to datasette.client.post(...) - as a _csrf_from= parameter (with an underscore because it's mainly intended for use in tests, though perhaps that's a weird convention that I shouldn't introduce).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Alternative, async-friendly pattern for `make_app_client()` and similar - fully retire `TestClient` 1500636982  

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,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);