issue_comments
3 rows where "created_at" is on date 2022-01-13, issue = 1100015398, reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- Maybe let plugins define custom serve options? · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1012506595 | https://github.com/simonw/datasette/issues/1591#issuecomment-1012506595 | https://api.github.com/repos/simonw/datasette/issues/1591 | IC_kwDOBm6k_c48WZ_j | simonw 9599 | 2022-01-13T20:52:56Z | 2022-01-13T20:52:56Z | OWNER | You can already run Or I could even have available plugin settings show up as a list at the bottom of the
|
{ "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 | |
1012505706 | https://github.com/simonw/datasette/issues/1591#issuecomment-1012505706 | https://api.github.com/repos/simonw/datasette/issues/1591 | IC_kwDOBm6k_c48WZxq | simonw 9599 | 2022-01-13T20:51:30Z | 2022-01-13T20:51:30Z | OWNER | Another option: if I make plugin settings a higher level concept in Datasette than they are at the moment, I could allow them to be set either using I want to make changes to that anyway, because I'm increasingly uncomfortable with plugin settings ending up in the "metadata" mechanism. |
{ "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 | |
1012504251 | https://github.com/simonw/datasette/issues/1591#issuecomment-1012504251 | https://api.github.com/repos/simonw/datasette/issues/1591 | IC_kwDOBm6k_c48WZa7 | simonw 9599 | 2022-01-13T20:49:19Z | 2022-01-13T20:49:59Z | OWNER | I try to stick pretty closely to what Click supports, and Click likes you to define options explicitly so that it can display them in the output of But... that makes me think that actually showing these options in The alternative would be to allow plugins to register their extra options with the command - which would mean the help output could look like this instead:
|
{ "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
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]);
user 1