issue_comments

Table actions

1 row where issue = 1181432624 and user = 9599 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

  • simonw · 1 ✖

issue 1

  • [plugins][documentation] Is it possible to serve per-plugin static folders when writing one-off (single file) plugins? · 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
1079582485 https://github.com/simonw/datasette/issues/1688#issuecomment-1079582485 https://api.github.com/repos/simonw/datasette/issues/1688 IC_kwDOBm6k_c5AWR8V simonw 9599 2022-03-26T03:15:34Z 2022-03-26T03:15:34Z OWNER

Yup, you're right in what you figured out here: stand-alone plugins can't currently package static assets other then using the static folder.

The datasette-plugin cookiecutter template should make creating a Python package pretty easy though: https://github.com/simonw/datasette-plugin

You can run that yourself, or you can run it using this GitHub template repository: https://github.com/simonw/datasette-plugin-template-repository 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 [plugins][documentation] Is it possible to serve per-plugin static folders when writing one-off (single file) plugins? 1181432624  

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