github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/648#issuecomment-563001064 | https://api.github.com/repos/simonw/datasette/issues/648 | 563001064 | MDEyOklzc3VlQ29tbWVudDU2MzAwMTA2NA== | 9599 | 2019-12-08T22:09:20Z | 2019-12-08T22:09:20Z | OWNER | Stretch goal: it would be neat if these pages could return custom HTTP headers (eg content-type) and maybe even status codes (eg for redirects) somehow. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
534492501 | |
https://github.com/simonw/datasette/issues/648#issuecomment-563000942 | https://api.github.com/repos/simonw/datasette/issues/648 | 563000942 | MDEyOklzc3VlQ29tbWVudDU2MzAwMDk0Mg== | 9599 | 2019-12-08T22:08:14Z | 2019-12-08T22:08:14Z | OWNER | Alternative idea: a new concept of "pages" which live inside `templates/pages/` and where the file name minus the `.html` extension defines the URL. `templates/about/me.html` would be served at `/about/me` - but only if no matching database and table were found. This only takes effect on 404 errors from core Datasette. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
534492501 | |
https://github.com/simonw/datasette/issues/648#issuecomment-562913040 | https://api.github.com/repos/simonw/datasette/issues/648 | 562913040 | MDEyOklzc3VlQ29tbWVudDU2MjkxMzA0MA== | 9599 | 2019-12-08T04:56:43Z | 2019-12-08T04:56:43Z | OWNER | Idea: do this with a simple template naming convention. If you hit `/about` and there is no matching database, check for a template file called `about-page.html`. If it exists, render it. Otherwise return a 404 database not found. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
534492501 |