issue_comments
43 rows where "updated_at" is on date 2020-06-09
This data as json, CSV (advanced)
Suggested facets: created_at (date)
| id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 638301073 | https://github.com/simonw/datasette/issues/797#issuecomment-638301073 | https://api.github.com/repos/simonw/datasette/issues/797 | MDEyOklzc3VlQ29tbWVudDYzODMwMTA3Mw== | simonw 9599 | 2020-06-03T16:14:54Z | 2020-06-09T04:00:40Z | OWNER | I want a unit test that exercises this for both writable and regular canned queries. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Documentation for new "params" setting for canned queries 630120235 | |
| 640951947 | https://github.com/simonw/datasette/issues/813#issuecomment-640951947 | https://api.github.com/repos/simonw/datasette/issues/813 | MDEyOklzc3VlQ29tbWVudDY0MDk1MTk0Nw== | simonw 9599 | 2020-06-09T00:09:56Z | 2020-06-09T00:09:56Z | OWNER | Documentation: https://datasette.readthedocs.io/en/latest/authentication.html#controlling-the-ability-to-execute-arbitrary-sql | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Mechanism for specifying allow_sql permission in metadata.json 634139848 | |
| 640955788 | https://github.com/simonw/datasette/issues/777#issuecomment-640955788 | https://api.github.com/repos/simonw/datasette/issues/777 | MDEyOklzc3VlQ29tbWVudDY0MDk1NTc4OA== | simonw 9599 | 2020-06-09T00:23:26Z | 2020-06-09T00:23:57Z | OWNER | Clue: https://latest.datasette.io/404 displays correctly but https://latest.datasette.io/fixtures/404 does not. That's because `<link rel="stylesheet" href="-/static/app.css?">` does the correct thing if you are on the root of the site but not if you are in a sub-directory. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Error pages not correctly loading CSS 626171242 | |
| 640957423 | https://github.com/simonw/datasette/issues/777#issuecomment-640957423 | https://api.github.com/repos/simonw/datasette/issues/777 | MDEyOklzc3VlQ29tbWVudDY0MDk1NzQyMw== | simonw 9599 | 2020-06-09T00:29:03Z | 2020-06-09T00:29:03Z | OWNER | Here's why: https://github.com/simonw/datasette/blob/49d6d2f7b0f6cb02e25022e1c9403811f1fa0a7c/datasette/app.py#L1024-L1029 404 errors are rendered by looking for a template from `["404.html", "500.html"]`. `404.html` doesn't actually ship with Datasette (plugins or custom template directories can provide it). So the `500.html` template is used. That template extends `base.html`, which expects there to be `base_url` and `app_css_hash` variables. But as you can see in the excerpt above, those variables are not being passed to the template context when the error page is rendered. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Error pages not correctly loading CSS 626171242 | |
| 640960553 | https://github.com/simonw/datasette/issues/215#issuecomment-640960553 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk2MDU1Mw== | simonw 9599 | 2020-06-09T00:41:09Z | 2020-06-09T00:41:09Z | OWNER | I'm going to imitate `register_output_renderer` and `register_facet_classes` - both return a list of things to register. So I'll do this: ```python @hookspec def register_routes(): "Register URL routes. Return a list of (regex, view_function) pairs" ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Allow plugins to define additional URL routes and views 314506669 | |
| 640960667 | https://github.com/simonw/datasette/issues/215#issuecomment-640960667 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk2MDY2Nw== | simonw 9599 | 2020-06-09T00:41:35Z | 2020-06-09T00:41:35Z | OWNER | I'm going to implement this one documentation-first in a pull request. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Allow plugins to define additional URL routes and views 314506669 | |
| 640971470 | https://github.com/simonw/datasette/issues/215#issuecomment-640971470 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk3MTQ3MA== | simonw 9599 | 2020-06-09T01:19:44Z | 2020-06-09T01:19:44Z | OWNER | I'll need to add documentation of the `Response` object (and `Response.html()` and `Response.text()` class methods - I should add `Response.json()` too) to the internals page https://datasette.readthedocs.io/en/stable/internals.html | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Allow plugins to define additional URL routes and views 314506669 | |
| 640972952 | https://github.com/simonw/datasette/issues/215#issuecomment-640972952 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MDk3Mjk1Mg== | simonw 9599 | 2020-06-09T01:24:52Z | 2020-06-09T01:25:33Z | OWNER | WIP documentation: https://github.com/simonw/datasette/blob/770dedb21adfc706592e6b5cdf5e751a8720fdf9/docs/plugins.rst#register_routes | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Allow plugins to define additional URL routes and views 314506669 | |
| 640982533 | https://github.com/simonw/datasette/issues/820#issuecomment-640982533 | https://api.github.com/repos/simonw/datasette/issues/820 | MDEyOklzc3VlQ29tbWVudDY0MDk4MjUzMw== | simonw 9599 | 2020-06-09T02:00:21Z | 2020-06-09T02:00:21Z | OWNER | In the case of registering API tokens it would be useful if the plugin could call a writable canned query which knows how to insert a randomly generated value. This could be achieved using a custom SQL function. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Idea: Plugin hook for registering canned queries 635049296 | |
| 641002504 | https://github.com/simonw/datasette/issues/215#issuecomment-641002504 | https://api.github.com/repos/simonw/datasette/issues/215 | MDEyOklzc3VlQ29tbWVudDY0MTAwMjUwNA== | simonw 9599 | 2020-06-09T03:14:32Z | 2020-06-09T03:14:32Z | OWNER | Documentation: https://datasette.readthedocs.io/en/latest/plugins.html#register-routes | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Allow plugins to define additional URL routes and views 314506669 | |
| 641003237 | https://github.com/simonw/datasette/issues/822#issuecomment-641003237 | https://api.github.com/repos/simonw/datasette/issues/822 | MDEyOklzc3VlQ29tbWVudDY0MTAwMzIzNw== | simonw 9599 | 2020-06-09T03:17:32Z | 2020-06-09T03:17:32Z | OWNER | Currently querystring parameters are accessed through `request.args` and POST variables through `request.post_vars()`. Would be good to have a name that was somewhat consistent with those. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | request.url_vars helper property 635077656 | |
| 641003291 | https://github.com/simonw/datasette/issues/822#issuecomment-641003291 | https://api.github.com/repos/simonw/datasette/issues/822 | MDEyOklzc3VlQ29tbWVudDY0MTAwMzI5MQ== | simonw 9599 | 2020-06-09T03:17:43Z | 2020-06-09T03:17:43Z | OWNER | I'm leaning towards `request.url_vars`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | request.url_vars helper property 635077656 | |
| 641009442 | https://github.com/simonw/datasette/issues/818#issuecomment-641009442 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAwOTQ0Mg== | simonw 9599 | 2020-06-09T03:41:55Z | 2020-06-09T03:41:55Z | OWNER | I want to build a plugin that does `Authorization: Bearer xxx` API key authentication. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Example permissions plugin 634917088 | |
| 641009744 | https://github.com/simonw/datasette/issues/818#issuecomment-641009744 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAwOTc0NA== | simonw 9599 | 2020-06-09T03:43:18Z | 2020-06-09T03:43:18Z | OWNER | `datasette-auth-bearer` perhaps? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Example permissions plugin 634917088 | |
| 641013524 | https://github.com/simonw/datasette/issues/818#issuecomment-641013524 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAxMzUyNA== | simonw 9599 | 2020-06-09T03:57:38Z | 2020-06-09T04:00:24Z | OWNER | Problem with that is it's more of a `actor_from_request` opportunity than `permission_allowed`. You could use `actor_from_request` to authenticate API clients from their `Authorization:` header, then use the regular `"allow"` blocks in `metadata.json` to actually assign their permissions. The most interesting permissions plugin would be one that implements permissions against some kind of database schema, hence allowing admins to edit permissions through writable canned queries. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Example permissions plugin 634917088 | |
| 641017721 | https://github.com/simonw/datasette/issues/805#issuecomment-641017721 | https://api.github.com/repos/simonw/datasette/issues/805 | MDEyOklzc3VlQ29tbWVudDY0MTAxNzcyMQ== | simonw 9599 | 2020-06-09T04:16:28Z | 2020-06-09T04:16:28Z | OWNER | Create `data.db` with: ``` echo '{"emoji": "🐯", "score": 0}' | sqlite-utils insert data.db emojis --pk=emoji - echo '{"emoji": "🐺", "score": 0}' | sqlite-utils insert data.db emojis --pk=emoji - ``` Then run Datasette with this `metadata.yaml`: ```yaml title: Datasette Poll databases: data: queries: vote: sql: |- update emojis set score = score + 1 where emoji = :emoji write: true ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Writable canned queries live demo on Glitch 632724154 | |
| 641017851 | https://github.com/simonw/datasette/issues/805#issuecomment-641017851 | https://api.github.com/repos/simonw/datasette/issues/805 | MDEyOklzc3VlQ29tbWVudDY0MTAxNzg1MQ== | simonw 9599 | 2020-06-09T04:17:00Z | 2020-06-09T04:17:00Z | OWNER | I can't get Datasette working on Glitch installed from a URL - I'm going to try this on Glitch once I've shipped the 0.44 release in #806. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Writable canned queries live demo on Glitch 632724154 | |
| 641025760 | https://github.com/simonw/datasette/issues/823#issuecomment-641025760 | https://api.github.com/repos/simonw/datasette/issues/823 | MDEyOklzc3VlQ29tbWVudDY0MTAyNTc2MA== | simonw 9599 | 2020-06-09T04:48:40Z | 2020-06-09T04:48:40Z | OWNER | I should assert that `"id"` exists and is a string in the code that calls the `actor_from_request` hook. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Documentation is inconsistent about "id" as required field on actor 635107393 | |
| 641026230 | https://github.com/simonw/datasette/issues/818#issuecomment-641026230 | https://api.github.com/repos/simonw/datasette/issues/818 | MDEyOklzc3VlQ29tbWVudDY0MTAyNjIzMA== | simonw 9599 | 2020-06-09T04:50:24Z | 2020-06-09T04:50:24Z | OWNER | I'm dropping this from the 0.44 milestone. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Example permissions plugin 634917088 | |
| 641026726 | https://github.com/simonw/datasette/issues/806#issuecomment-641026726 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTAyNjcyNg== | simonw 9599 | 2020-06-09T04:52:07Z | 2020-06-09T04:52:07Z | OWNER | Changelog for this is going to be huge - 96 commits since 0.43 already! https://github.com/simonw/datasette/compare/0.43...master | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release Datasette 0.44 632753851 | |
| 641059221 | https://github.com/simonw/datasette/issues/823#issuecomment-641059221 | https://api.github.com/repos/simonw/datasette/issues/823 | MDEyOklzc3VlQ29tbWVudDY0MTA1OTIyMQ== | simonw 9599 | 2020-06-09T06:23:51Z | 2020-06-09T06:24:09Z | OWNER | I don't like the "id" requirement. I can think of plenty of situations where a unique ID might not be available: - auth against an external token - an email address or a phone number for example - auth using encrypted tokens - where decrypting the token tells you exactly what permissions that token should have, like in https://blog.thea.codes/building-a-stateless-api-proxy/ | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Documentation is inconsistent about "id" as required field on actor 635107393 | |
| 641062164 | https://github.com/simonw/datasette/issues/825#issuecomment-641062164 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTA2MjE2NA== | simonw 9599 | 2020-06-09T06:30:24Z | 2020-06-09T14:05:33Z | OWNER | Idea: the anonymous actor could be passed to `actor_matches_allow()` as: ```json {"anonymous": true} ``` Then allow blocks like this could be used to allow them: ```json { "plugins": { "datasette-upload-csvs": { "allow": { "anonymous": true } } } } ``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Way to enable a default=False permission for anonymous users 635147716 | |
| 641320947 | https://github.com/simonw/datasette/issues/825#issuecomment-641320947 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTMyMDk0Nw== | simonw 9599 | 2020-06-09T14:06:46Z | 2020-06-09T14:06:46Z | OWNER | I'm torn between `anonymous` and `anon` - because the latter is less typing, and I envisage people writing a lot of code like this: ```python if actor.get("anonymous"): # ... ``` I'm going with `anonymous` because it's that tiny bit clearer than `anon`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Way to enable a default=False permission for anonymous users 635147716 | |
| 641353186 | https://github.com/simonw/datasette/issues/823#issuecomment-641353186 | https://api.github.com/repos/simonw/datasette/issues/823 | MDEyOklzc3VlQ29tbWVudDY0MTM1MzE4Ng== | simonw 9599 | 2020-06-09T14:58:36Z | 2020-06-09T14:58:36Z | OWNER | Docs now say: > The actor dictionary can be any shape - the design of that data structure is left up to the plugins. A useful convention is to include an `"id"` string, as demonstrated by the "root" actor below. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Documentation is inconsistent about "id" as required field on actor 635107393 | |
| 641353729 | https://github.com/simonw/datasette/issues/812#issuecomment-641353729 | https://api.github.com/repos/simonw/datasette/issues/812 | MDEyOklzc3VlQ29tbWVudDY0MTM1MzcyOQ== | simonw 9599 | 2020-06-09T14:59:25Z | 2020-06-09T14:59:25Z | OWNER | I'm going to figure this out by working with https://github.com/simonw/datasette-auth-github/issues/62 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to customize what happens when a view permission fails 634112607 | |
| 641359103 | https://github.com/simonw/datasette/issues/826#issuecomment-641359103 | https://api.github.com/repos/simonw/datasette/issues/826 | MDEyOklzc3VlQ29tbWVudDY0MTM1OTEwMw== | simonw 9599 | 2020-06-09T15:08:07Z | 2020-06-09T15:10:33Z | OWNER | I should probably add a utility function for setting that cookie - right now the only code that does that is here: https://github.com/simonw/datasette/blob/dfff34e1987976e72f58ee7b274952840b1f4b71/datasette/views/special.py#L63-L76 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Document the ds_actor signed cookie 635519358 | |
| 641360187 | https://github.com/simonw/datasette/issues/826#issuecomment-641360187 | https://api.github.com/repos/simonw/datasette/issues/826 | MDEyOklzc3VlQ29tbWVudDY0MTM2MDE4Nw== | simonw 9599 | 2020-06-09T15:10:00Z | 2020-06-09T15:11:24Z | OWNER | Also a good reminder that I need a `set_cookie()` function (#795) so I don't have to mess around with `SimpleCookie` directly. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Document the ds_actor signed cookie 635519358 | |
| 641361311 | https://github.com/simonw/datasette/issues/795#issuecomment-641361311 | https://api.github.com/repos/simonw/datasette/issues/795 | MDEyOklzc3VlQ29tbWVudDY0MTM2MTMxMQ== | simonw 9599 | 2020-06-09T15:11:50Z | 2020-06-09T15:11:50Z | OWNER | Also: https://github.com/simonw/datasette/blob/dfff34e1987976e72f58ee7b274952840b1f4b71/datasette/views/special.py#L63-L76 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | response.set_cookie() method 629541395 | |
| 641406944 | https://github.com/simonw/datasette/issues/825#issuecomment-641406944 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQwNjk0NA== | simonw 9599 | 2020-06-09T16:12:02Z | 2020-06-09T17:19:19Z | OWNER | Alternative design: leave actor alone. Instead specify that allow blocks can look like this: ```json { "allow": { "unauthenticated": true } } ``` I like this: the above block is very self-documenting. The `"id": "*"` mechanism means there is already precedent for allow keys with special meaning. **I'm going with this design.** | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Way to enable a default=False permission for anonymous users 635147716 | |
| 641412424 | https://github.com/simonw/datasette/issues/825#issuecomment-641412424 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQxMjQyNA== | simonw 9599 | 2020-06-09T16:22:07Z | 2020-06-09T16:22:07Z | OWNER | When I implement this I should also document default allow vs default deny as a concept, and specify that default next to every documented permission. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Way to enable a default=False permission for anonymous users 635147716 | |
| 641449725 | https://github.com/simonw/datasette/issues/825#issuecomment-641449725 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQ0OTcyNQ== | simonw 9599 | 2020-06-09T17:02:31Z | 2020-06-09T17:02:31Z | OWNER | Documented at the bottom of this section: https://github.com/simonw/datasette/blob/7633b9ab249b2dce5ee0b4fcf9542c13a1703ef0/docs/authentication.rst#defining-permissions-with-allow-blocks | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Way to enable a default=False permission for anonymous users 635147716 | |
| 641452563 | https://github.com/simonw/datasette/issues/825#issuecomment-641452563 | https://api.github.com/repos/simonw/datasette/issues/825 | MDEyOklzc3VlQ29tbWVudDY0MTQ1MjU2Mw== | simonw 9599 | 2020-06-09T17:08:00Z | 2020-06-09T17:08:00Z | OWNER | https://datasette.readthedocs.io/en/latest/authentication.html#defining-permissions-with-allow-blocks | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Way to enable a default=False permission for anonymous users 635147716 | |
| 641528269 | https://github.com/simonw/datasette/issues/827#issuecomment-641528269 | https://api.github.com/repos/simonw/datasette/issues/827 | MDEyOklzc3VlQ29tbWVudDY0MTUyODI2OQ== | simonw 9599 | 2020-06-09T19:38:30Z | 2020-06-09T19:38:30Z | OWNER | https://datasette.readthedocs.io/en/latest/internals.html#csrf-protection | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Document CSRF protection (for plugins) 635696400 | |
| 641528737 | https://github.com/simonw/datasette/issues/804#issuecomment-641528737 | https://api.github.com/repos/simonw/datasette/issues/804 | MDEyOklzc3VlQ29tbWVudDY0MTUyODczNw== | simonw 9599 | 2020-06-09T19:39:24Z | 2020-06-09T19:39:24Z | OWNER | Switched to 0.44 milestone because I don't like shipping releases with known bugs. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | python tests/fixtures.py command has a bug 632673972 | |
| 641538799 | https://github.com/simonw/datasette/issues/804#issuecomment-641538799 | https://api.github.com/repos/simonw/datasette/issues/804 | MDEyOklzc3VlQ29tbWVudDY0MTUzODc5OQ== | simonw 9599 | 2020-06-09T20:01:08Z | 2020-06-09T20:01:08Z | OWNER | $ python tests/fixtures.py fixtures.db fixtures-metadata.json fixtures-plugins Test tables written to fixtures.db - metadata written to fixtures-metadata.json Wrote plugin: fixtures-plugins/register_output_renderer.py Wrote plugin: fixtures-plugins/view_name.py Wrote plugin: fixtures-plugins/my_plugin.py Wrote plugin: fixtures-plugins/messages_output_renderer.py Wrote plugin: fixtures-plugins/my_plugin_2.py | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | python tests/fixtures.py command has a bug 632673972 | |
| 641538982 | https://github.com/simonw/datasette/issues/804#issuecomment-641538982 | https://api.github.com/repos/simonw/datasette/issues/804 | MDEyOklzc3VlQ29tbWVudDY0MTUzODk4Mg== | simonw 9599 | 2020-06-09T20:01:30Z | 2020-06-09T20:01:30Z | OWNER | Now fully documented here: https://datasette.readthedocs.io/en/latest/contributing.html#setting-up-a-development-environment | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | python tests/fixtures.py command has a bug 632673972 | |
| 641602794 | https://github.com/simonw/datasette/issues/806#issuecomment-641602794 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYwMjc5NA== | simonw 9599 | 2020-06-09T21:55:45Z | 2020-06-09T21:55:45Z | OWNER | Last-minute thought: Should I worry about calling permissions "actions", when I have an idea for a future plugin hook that allows plugins to add something I was going to call "actions" to database, table and row pages? Those actions would take the form of menu item commands that Do Something to the selected object. If I use "actions" to mean permission names, will I be able to find a good alternative name for these dynamic menu items? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release Datasette 0.44 632753851 | |
| 641603457 | https://github.com/simonw/datasette/issues/806#issuecomment-641603457 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYwMzQ1Nw== | simonw 9599 | 2020-06-09T21:57:32Z | 2020-06-09T21:57:32Z | OWNER | operation, procedure, process as alternative words for those menu items? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release Datasette 0.44 632753851 | |
| 641604210 | https://github.com/simonw/datasette/issues/806#issuecomment-641604210 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYwNDIxMA== | simonw 9599 | 2020-06-09T21:59:33Z | 2020-06-09T22:00:11Z | OWNER | AWS IAM uses action and resource terminology: https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_access-management.html - I think that's where I got that language: > ```json > { > "Version": "2012-10-17", > "Statement": { > "Effect": "Allow", > "Action": "dynamodb:*", > "Resource": "arn:aws:dynamodb:us-east-2:123456789012:table/Books" > } > } > ``` I'm going to stick with "action" in its current meaning. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release Datasette 0.44 632753851 | |
| 641616060 | https://github.com/simonw/datasette/issues/826#issuecomment-641616060 | https://api.github.com/repos/simonw/datasette/issues/826 | MDEyOklzc3VlQ29tbWVudDY0MTYxNjA2MA== | simonw 9599 | 2020-06-09T22:33:12Z | 2020-06-09T22:33:12Z | OWNER | https://datasette.readthedocs.io/en/latest/authentication.html#the-ds-actor-cookie | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Document the ds_actor signed cookie 635519358 | |
| 641616185 | https://github.com/simonw/datasette/issues/795#issuecomment-641616185 | https://api.github.com/repos/simonw/datasette/issues/795 | MDEyOklzc3VlQ29tbWVudDY0MTYxNjE4NQ== | simonw 9599 | 2020-06-09T22:33:33Z | 2020-06-09T22:33:33Z | OWNER | Documentation: https://datasette.readthedocs.io/en/latest/internals.html#setting-cookies-with-response-set-cookie | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | response.set_cookie() method 629541395 | |
| 641634749 | https://github.com/simonw/datasette/issues/806#issuecomment-641634749 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYzNDc0OQ== | simonw 9599 | 2020-06-09T23:34:52Z | 2020-06-09T23:34:52Z | OWNER | Preview of the release notes is now available here: https://datasette.readthedocs.io/en/latest/changelog.html#v0-44 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release Datasette 0.44 632753851 | |
| 641637696 | https://github.com/simonw/datasette/issues/806#issuecomment-641637696 | https://api.github.com/repos/simonw/datasette/issues/806 | MDEyOklzc3VlQ29tbWVudDY0MTYzNzY5Ng== | simonw 9599 | 2020-06-09T23:46:00Z | 2020-06-09T23:46:00Z | OWNER | The issues that should be referenced from this release are: #395, #519, #576, #699, #706, #774, #777, #781, #784, #788, #790, #797, #798, #800, #802, #804, #819, #822 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Release Datasette 0.44 632753851 |
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]);