issue_comments
3 rows where "updated_at" is on date 2019-12-09 sorted by issue_url
This data as json, CSV (advanced)
Suggested facets: created_at (date)
id | html_url | issue_url ▼ | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
563449488 | https://github.com/simonw/datasette/issues/577#issuecomment-563449488 | https://api.github.com/repos/simonw/datasette/issues/577 | MDEyOklzc3VlQ29tbWVudDU2MzQ0OTQ4OA== | simonw 9599 | 2019-12-09T21:32:47Z | 2019-12-09T21:32:47Z | OWNER | I'm going to go with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Utility mechanism for plugins to render templates 497171390 | |
563015290 | https://github.com/simonw/datasette/issues/648#issuecomment-563015290 | https://api.github.com/repos/simonw/datasette/issues/648 | MDEyOklzc3VlQ29tbWVudDU2MzAxNTI5MA== | simonw 9599 | 2019-12-09T00:18:17Z | 2019-12-09T00:18:17Z | OWNER | The implementation in https://github.com/simonw/datasette/commit/c5e8cd84d3ef55ed86771ac0bde0ca91d6b0e07a acts as a proof of concept. It has a big flaw though: it doesn't reuse the regular render() mechanism, which means it doesn't register custom template tags from plugins. This is bad because it means that pages rendered in this way cannot take advantage of things like datasette-template-sql. This means this issue is likely dependent on #577 - a documented mechanism to allow plugins to render templates. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for adding arbitrary pages like /about 534492501 | |
563016016 | https://github.com/simonw/datasette/issues/650#issuecomment-563016016 | https://api.github.com/repos/simonw/datasette/issues/650 | MDEyOklzc3VlQ29tbWVudDU2MzAxNjAxNg== | simonw 9599 | 2019-12-09T00:24:20Z | 2019-12-09T00:24:20Z | OWNER | In the future I may write a script which extracts the terms from this document into a separate database table. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add a glossary to the documentation 534629631 |
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]);
issue 3