issue_comments
5 rows where issue = 529429214 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Provide a cookiecutter template for creating new plugins · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
646930160 | https://github.com/simonw/datasette/issues/642#issuecomment-646930160 | https://api.github.com/repos/simonw/datasette/issues/642 | MDEyOklzc3VlQ29tbWVudDY0NjkzMDE2MA== | simonw 9599 | 2020-06-20T03:20:25Z | 2020-06-20T03:20:25Z | OWNER | Shipped this today! https://github.com/simonw/datasette-plugin is a cookiecutter template for creating new plugins. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide a cookiecutter template for creating new plugins 529429214 | |
646930059 | https://github.com/simonw/datasette/issues/642#issuecomment-646930059 | https://api.github.com/repos/simonw/datasette/issues/642 | MDEyOklzc3VlQ29tbWVudDY0NjkzMDA1OQ== | simonw 9599 | 2020-06-20T03:19:57Z | 2020-06-20T03:19:57Z | OWNER | @psychemedia sorry I missed your comment before. Niche Museums is definitely the best example of custom templates at the moment: https://github.com/simonw/museums/tree/master/templates I want to comprehensively document the variables made available to custom templates before shipping Datasette 1.0 - just filed that as #857. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide a cookiecutter template for creating new plugins 529429214 | |
559146316 | https://github.com/simonw/datasette/issues/642#issuecomment-559146316 | https://api.github.com/repos/simonw/datasette/issues/642 | MDEyOklzc3VlQ29tbWVudDU1OTE0NjMxNg== | simonw 9599 | 2019-11-27T15:55:51Z | 2019-11-27T15:55:51Z | OWNER | One thing that put me off cookiecutter in the past is that I didn't think it could conditionally create files. I was wrong! You can use post- hooks to delete the files that you didn't need: https://github.com/audreyr/cookiecutter-pypackage/blob/master/hooks/post_gen_project.py I could use this mechanism to rename directories too if I needed to. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide a cookiecutter template for creating new plugins 529429214 | |
559143123 | https://github.com/simonw/datasette/issues/642#issuecomment-559143123 | https://api.github.com/repos/simonw/datasette/issues/642 | MDEyOklzc3VlQ29tbWVudDU1OTE0MzEyMw== | simonw 9599 | 2019-11-27T15:48:11Z | 2019-11-27T15:48:11Z | OWNER | This will also make bundling static files less error-prone. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide a cookiecutter template for creating new plugins 529429214 | |
559142893 | https://github.com/simonw/datasette/issues/642#issuecomment-559142893 | https://api.github.com/repos/simonw/datasette/issues/642 | MDEyOklzc3VlQ29tbWVudDU1OTE0Mjg5Mw== | simonw 9599 | 2019-11-27T15:47:36Z | 2019-11-27T15:47:42Z | OWNER | It can include options for quickly bootstrapping custom template function or SQL function plugins, which are really simple. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide a cookiecutter template for creating new plugins 529429214 |
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