issue_comments

Table actions

2 rows where issue = 1100015398 and "updated_at" is on date 2022-01-12 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Maybe let plugins define custom serve options? · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1010947634 https://github.com/simonw/datasette/issues/1591#issuecomment-1010947634 https://api.github.com/repos/simonw/datasette/issues/1591 IC_kwDOBm6k_c48QdYy psychemedia 82988 2022-01-12T11:32:17Z 2022-01-12T11:32:17Z CONTRIBUTOR

Is it possible to parse things like --ext-{plugin}-{arg} VALUE ?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Maybe let plugins define custom serve options? 1100015398  
1010764036 https://github.com/simonw/datasette/issues/1591#issuecomment-1010764036 https://api.github.com/repos/simonw/datasette/issues/1591 IC_kwDOBm6k_c48PwkE simonw 9599 2022-01-12T08:22:16Z 2022-01-12T08:22:32Z OWNER

The challenge here is avoiding clashes. What if a plugin adds an option that I later want to use for a new Datasette core feature? Or what if two plugins define the same option?

Maybe the solution is to make them use namespaces defined by the plugin name.

How about this:

datasette t.db --plugin-setting datasette-tiddlywiki db t.db

It's a bit verbose having an option that itself then takes THREE strings: plugin name, setting name, setting value - but it would work.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Maybe let plugins define custom serve options? 1100015398  

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