issue_comments

Table actions

3 rows where issue = 340039409 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

  • Ensure --help examples in docs are always up to date · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
407450815 https://github.com/simonw/datasette/issues/336#issuecomment-407450815 https://api.github.com/repos/simonw/datasette/issues/336 MDEyOklzc3VlQ29tbWVudDQwNzQ1MDgxNQ== simonw 9599 2018-07-24T15:35:03Z 2018-07-24T15:35:03Z OWNER

Actually I do like the idea of a unit test that reminds me if I've forgotten to update the included files.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ensure --help examples in docs are always up to date 340039409  
404021890 https://github.com/simonw/datasette/issues/336#issuecomment-404021890 https://api.github.com/repos/simonw/datasette/issues/336 MDEyOklzc3VlQ29tbWVudDQwNDAyMTg5MA== simonw 9599 2018-07-11T02:09:25Z 2018-07-11T02:09:25Z OWNER

I decided against the unit tests, instead I have a new script called ./update-docs-help.sh which I can run any time I want to refresh the included documentation: https://github.com/simonw/datasette/commit/aec3ae53237e43b0c268dbf9b58fa265ef38cfe1#diff-cb15a1e5a244bb82ad4afce67f252543

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ensure --help examples in docs are always up to date 340039409  
403996143 https://github.com/simonw/datasette/issues/336#issuecomment-403996143 https://api.github.com/repos/simonw/datasette/issues/336 MDEyOklzc3VlQ29tbWVudDQwMzk5NjE0Mw== simonw 9599 2018-07-10T23:21:27Z 2018-07-10T23:21:27Z OWNER

Easiest way to do this I think would be to make those help blocks separate files in the docs/ directory (publish-help.txt perhaps) and then include them with a sphinx directive: https://reinout.vanrees.org/weblog/2010/12/08/include-external-in-sphinx.html

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ensure --help examples in docs are always up to date 340039409  

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