issue_comments

Table actions

3 rows where author_association = "OWNER" and issue = 607107849 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

  • Configuration directory mode · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
619700113 https://github.com/simonw/datasette/pull/739#issuecomment-619700113 https://api.github.com/repos/simonw/datasette/issues/739 MDEyOklzc3VlQ29tbWVudDYxOTcwMDExMw== simonw 9599 2020-04-27T03:58:09Z 2020-04-27T03:58:09Z OWNER

I think documentation goes on https://datasette.readthedocs.io/en/stable/config.html - but I'm going to need to re-arrange that page to fit in a section about configuration directories.

I'll move the existing list of settings into a "configration options" section.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Configuration directory mode 607107849  
619678614 https://github.com/simonw/datasette/pull/739#issuecomment-619678614 https://api.github.com/repos/simonw/datasette/issues/739 MDEyOklzc3VlQ29tbWVudDYxOTY3ODYxNA== simonw 9599 2020-04-27T02:44:21Z 2020-04-27T02:44:21Z OWNER

I'm going to add a Datasette(config_dir=".") parameter which initializes from the given directory, allowing other parameters to over-ride it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Configuration directory mode 607107849  
619622311 https://github.com/simonw/datasette/pull/739#issuecomment-619622311 https://api.github.com/repos/simonw/datasette/issues/739 MDEyOklzc3VlQ29tbWVudDYxOTYyMjMxMQ== simonw 9599 2020-04-26T20:45:07Z 2020-04-26T20:45:07Z OWNER

I think ALL explicit options should over-ride options that were detected in the directory structure. This means my current implementation isn't quite right - using a class method makes it hard to merge the details with the explicit options passed to the CLI function.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Configuration directory mode 607107849  

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