issue_comments

Table actions

3 rows where issue = 276873891

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ html_url issue_url node_id user created_at updated_at author_association body reactions issue performed_via_github_app
348404988 https://github.com/simonw/datasette/issues/154#issuecomment-348404988 https://api.github.com/repos/simonw/datasette/issues/154 MDEyOklzc3VlQ29tbWVudDM0ODQwNDk4OA== simonw 9599 2017-12-01T05:27:40Z 2017-12-01T05:27:40Z OWNER If I do add additional static file bundling should that automatically get content hashes as well? #160 - problem with that is then I might have to parse the CSS files and rewrite their internal background-url references etc. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Datasette CSS should include content hash in the URL 276873891  
350302417 https://github.com/simonw/datasette/issues/154#issuecomment-350302417 https://api.github.com/repos/simonw/datasette/issues/154 MDEyOklzc3VlQ29tbWVudDM1MDMwMjQxNw== simonw 9599 2017-12-08T16:11:24Z 2017-12-08T16:11:24Z OWNER I think I'll do this as a custom Jinja template filter. That way template authors can re-use it for their own static files if they want. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Datasette CSS should include content hash in the URL 276873891  
350323722 https://github.com/simonw/datasette/issues/154#issuecomment-350323722 https://api.github.com/repos/simonw/datasette/issues/154 MDEyOklzc3VlQ29tbWVudDM1MDMyMzcyMg== simonw 9599 2017-12-08T17:35:25Z 2017-12-08T17:35:25Z OWNER If I do this as a querystring parameter I won't need to worry about URL routing. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Datasette CSS should include content hash in the URL 276873891  

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