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/160#issuecomment-348404864 | https://api.github.com/repos/simonw/datasette/issues/160 | 348404864 | MDEyOklzc3VlQ29tbWVudDM0ODQwNDg2NA== | 9599 | 2017-12-01T05:26:57Z | 2017-12-01T05:26:57Z | OWNER | Question is... what should happen to the default static stuff? At the moment that's just https://fivethirtyeight.datasettes.com/-/static/app.css - though I want to improve that to include a content hash, see #154 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
278208011 | |
https://github.com/simonw/datasette/issues/154#issuecomment-348404988 | https://api.github.com/repos/simonw/datasette/issues/154 | 348404988 | MDEyOklzc3VlQ29tbWVudDM0ODQwNDk4OA== | 9599 | 2017-12-01T05:27:40Z | 2017-12-01T05:27:40Z | OWNER | If I do add additional static file bundling should that automatically get content hashes as well? #160 - problem with that is then I might have to parse the CSS files and rewrite their internal background-url references etc. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
276873891 | |
https://github.com/simonw/datasette/issues/20#issuecomment-348420129 | https://api.github.com/repos/simonw/datasette/issues/20 | 348420129 | MDEyOklzc3VlQ29tbWVudDM0ODQyMDEyOQ== | 9599 | 2017-12-01T07:16:25Z | 2017-12-01T07:16:25Z | OWNER | I've found some examples of canned queries I want to support that can't be represented as views, so I'm going to reopen this. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267759136 | |
https://github.com/simonw/datasette/issues/20#issuecomment-348420955 | https://api.github.com/repos/simonw/datasette/issues/20 | 348420955 | MDEyOklzc3VlQ29tbWVudDM0ODQyMDk1NQ== | 9599 | 2017-12-01T07:21:08Z | 2017-12-01T07:21:08Z | OWNER | I'll use the existing metadata.json file: { "databases": { "mydb": { "queries": { "custom_thingy": {... The query definition can either be just a string of SQL, or it can be an object with a sql key and optional title and description keys. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267759136 |