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/153#issuecomment-347050235 | https://api.github.com/repos/simonw/datasette/issues/153 | 347050235 | MDEyOklzc3VlQ29tbWVudDM0NzA1MDIzNQ== | 9599 | 2017-11-27T00:06:24Z | 2017-11-27T00:06:24Z | OWNER | I've been thinking about 1. a bit - I actually think it would be fine to have a rule that says "if the contents of the cell starts with `http://` or `https://` and doesn't contain any whitespace, turn that into a link". If you need the non-linked version that will always be available in the JSON. For the other two... I think #12 may be the way to go here: if you can easily over-ride the `row.html` and `table.html` templates for specific databases you can easily set pre-formatted text or similar for certain values - maybe even with CSS that targets a specific table column. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
276842536 | |
https://github.com/simonw/datasette/issues/153#issuecomment-347051331 | https://api.github.com/repos/simonw/datasette/issues/153 | 347051331 | MDEyOklzc3VlQ29tbWVudDM0NzA1MTMzMQ== | 9599 | 2017-11-27T00:23:40Z | 2017-11-27T03:58:49Z | OWNER | One quick fix could be to add a `extra_css_url` key to the `metadata.json` format (which currently hosts `title`, `license_url` etc) - if populated, we can inject a link to that stylesheet on every page. We could add a few classes in strategic places that include the database and table names to give people styling hooks. While we're at it, an `extra_js_url` key would let people go really nuts! | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
276842536 |