issue_comments
8 rows where author_association = "OWNER", "created_at" is on date 2022-01-19 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 8 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1016639294 | https://github.com/simonw/datasette/issues/1601#issuecomment-1016639294 | https://api.github.com/repos/simonw/datasette/issues/1601 | IC_kwDOBm6k_c48mK8- | simonw 9599 | 2022-01-19T16:26:44Z | 2022-01-20T03:57:17Z | OWNER | I need to add |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add KNN and data_licenses to hidden tables list 1105916061 | |
1016977725 | https://github.com/simonw/datasette/issues/1605#issuecomment-1016977725 | https://api.github.com/repos/simonw/datasette/issues/1605 | IC_kwDOBm6k_c48ndk9 | simonw 9599 | 2022-01-19T23:55:08Z | 2022-01-19T23:55:08Z | OWNER | Oh that's interesting. I was thinking about this from a slightly different angle recently - pondering what a static site generator built on top of Datasette might look like. Just a sketch at the moment, but I was imagining a YAML configuration file with a SQL query that returns a list of paths - then a tool that runs that query and uses the equivalent of I think these two ideas can probably be merged. I'd love to know more about how you are solving this right now! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Scripted exports 1108671952 | |
1016637722 | https://github.com/simonw/datasette/issues/1601#issuecomment-1016637722 | https://api.github.com/repos/simonw/datasette/issues/1601 | IC_kwDOBm6k_c48mKka | simonw 9599 | 2022-01-19T16:25:07Z | 2022-01-19T16:25:07Z | OWNER | Good idea - though I'm nervous about accidentally hiding a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add KNN and data_licenses to hidden tables list 1105916061 | |
1016636561 | https://github.com/simonw/datasette/issues/1604#issuecomment-1016636561 | https://api.github.com/repos/simonw/datasette/issues/1604 | IC_kwDOBm6k_c48mKSR | simonw 9599 | 2022-01-19T16:23:54Z | 2022-01-19T16:23:54Z | OWNER | Potential design:
I think I'm OK with calling this This will require Not sure how best to handle the DNS part - maybe print out instructions for the necessary CNAME? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Option to assign a domain/subdomain using `datasette publish cloudrun` 1108300685 | |
1016589519 | https://github.com/simonw/datasette/issues/1603#issuecomment-1016589519 | https://api.github.com/repos/simonw/datasette/issues/1603 | IC_kwDOBm6k_c48l-zP | simonw 9599 | 2022-01-19T15:36:38Z | 2022-01-19T15:36:38Z | OWNER | Also people can use a custom base template and link to a custom favicon if they want to. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
A proper favicon 1108235694 | |
1016589140 | https://github.com/simonw/datasette/issues/1603#issuecomment-1016589140 | https://api.github.com/repos/simonw/datasette/issues/1603 | IC_kwDOBm6k_c48l-tU | simonw 9599 | 2022-01-19T15:36:16Z | 2022-01-19T15:36:16Z | OWNER | For the moment then I will hard-code a new favicon and leave it to ASGI plugins if people want to define their own. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
A proper favicon 1108235694 | |
1016588326 | https://github.com/simonw/datasette/issues/1603#issuecomment-1016588326 | https://api.github.com/repos/simonw/datasette/issues/1603 | IC_kwDOBm6k_c48l-gm | simonw 9599 | 2022-01-19T15:35:33Z | 2022-01-19T15:35:33Z | OWNER | I don't think abusing the template loader mechanism for this will work: Jinja provides an API for loading text templates, but I don't think it can be sensibly abused to open binary image files instead. Loaded code is here: https://github.com/pallets/jinja/blob/main/src/jinja2/loaders.py |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
A proper favicon 1108235694 | |
1016579661 | https://github.com/simonw/datasette/issues/1603#issuecomment-1016579661 | https://api.github.com/repos/simonw/datasette/issues/1603 | IC_kwDOBm6k_c48l8ZN | simonw 9599 | 2022-01-19T15:27:05Z | 2022-01-19T15:27:05Z | OWNER | I'd like this to be customizable. I'm going to load it from the template loading system such that a custom favicon for a specific instance can be dropped in using a file in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
A proper favicon 1108235694 |
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 4