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/14#issuecomment-383140111 | https://api.github.com/repos/simonw/datasette/issues/14 | 383140111 | MDEyOklzc3VlQ29tbWVudDM4MzE0MDExMQ== | 9599 | 2018-04-20T15:52:33Z | 2018-04-20T15:52:33Z | OWNER | Here's a link demonstrating my new plugin: https://datasette-cluster-map-demo.now.sh/polar-bears-455fe3a/USGS_WC_eartags_output_files_2009-2011-Status | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 | |
https://github.com/simonw/datasette/issues/14#issuecomment-383139889 | https://api.github.com/repos/simonw/datasette/issues/14 | 383139889 | MDEyOklzc3VlQ29tbWVudDM4MzEzOTg4OQ== | 9599 | 2018-04-20T15:51:47Z | 2018-04-20T15:51:47Z | OWNER | I released everything we have so far in [Datasette 0.20](https://github.com/simonw/datasette/releases/tag/0.20) and built and released an example plugin, [datasette-cluster-map](https://pypi.org/project/datasette-cluster-map/). Here's my blog entry about it: https://simonwillison.net/2018/Apr/20/datasette-plugins/ | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 | |
https://github.com/simonw/datasette/issues/230#issuecomment-383109984 | https://api.github.com/repos/simonw/datasette/issues/230 | 383109984 | MDEyOklzc3VlQ29tbWVudDM4MzEwOTk4NA== | 9599 | 2018-04-20T14:15:39Z | 2018-04-20T14:15:39Z | OWNER | Refs #229 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
316128955 | |
https://github.com/simonw/datasette/issues/227#issuecomment-382967238 | https://api.github.com/repos/simonw/datasette/issues/227 | 382967238 | MDEyOklzc3VlQ29tbWVudDM4Mjk2NzIzOA== | 9599 | 2018-04-20T03:58:09Z | 2018-04-20T03:58:09Z | OWNER | Maybe prepare_table_data() vs prepare_table_context() | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
315960272 | |
https://github.com/simonw/datasette/issues/227#issuecomment-382966604 | https://api.github.com/repos/simonw/datasette/issues/227 | 382966604 | MDEyOklzc3VlQ29tbWVudDM4Mjk2NjYwNA== | 9599 | 2018-04-20T03:54:56Z | 2018-04-20T03:54:56Z | OWNER | Should this differentiate between preparing the data to be sent back as JSON and preparing the context for the template? | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
315960272 | |
https://github.com/simonw/datasette/issues/227#issuecomment-382964794 | https://api.github.com/repos/simonw/datasette/issues/227 | 382964794 | MDEyOklzc3VlQ29tbWVudDM4Mjk2NDc5NA== | 9599 | 2018-04-20T03:45:18Z | 2018-04-20T03:45:18Z | OWNER | What if the context needs to make await calls? One possible option: plugins can either manipulate the context in place OR they can return an awaitable. If they do that, the caller will await it. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
315960272 | |
https://github.com/simonw/datasette/issues/227#issuecomment-382959857 | https://api.github.com/repos/simonw/datasette/issues/227 | 382959857 | MDEyOklzc3VlQ29tbWVudDM4Mjk1OTg1Nw== | 9599 | 2018-04-20T03:21:43Z | 2018-04-20T03:21:43Z | OWNER | Plus a generic prepare_context() hook called in the common render method. prepare_context_table(), prepare_context_row() etc Arguments are context, request, self (hence can access self.ds) | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
315960272 | |
https://github.com/simonw/datasette/issues/227#issuecomment-382958693 | https://api.github.com/repos/simonw/datasette/issues/227 | 382958693 | MDEyOklzc3VlQ29tbWVudDM4Mjk1ODY5Mw== | 9599 | 2018-04-20T03:15:52Z | 2018-04-20T03:15:52Z | OWNER | A better way to do this would be with many different plugin hooks, one for each view. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
315960272 | |
https://github.com/simonw/datasette/issues/228#issuecomment-382924910 | https://api.github.com/repos/simonw/datasette/issues/228 | 382924910 | MDEyOklzc3VlQ29tbWVudDM4MjkyNDkxMA== | 9599 | 2018-04-20T00:35:48Z | 2018-04-20T00:35:48Z | OWNER | Hiding tables with the `idx_` prefix should be good enough here, since false positives aren't very harmful. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
316031566 |