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/1798#issuecomment-1234925975 | https://api.github.com/repos/simonw/datasette/issues/1798 | 1234925975 | IC_kwDOBm6k_c5Jm3mX | 9599 | 2022-09-02T00:02:53Z | 2022-09-02T00:02:53Z | OWNER | Here's a very old issue that suggests validating metadata: - https://github.com/simonw/datasette/issues/260 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1359557737 | |
https://github.com/simonw/datasette/issues/1798#issuecomment-1234925621 | https://api.github.com/repos/simonw/datasette/issues/1798 | 1234925621 | IC_kwDOBm6k_c5Jm3g1 | 9599 | 2022-09-02T00:01:47Z | 2022-09-02T00:01:47Z | OWNER | It's a nasty gotcha though. I'm inclined to add validation to Datasette that fails to start the server with an error if you attempt to start it with metadata that accidentally has a boolean where a database name is expected. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1359557737 | |
https://github.com/simonw/datasette/issues/1798#issuecomment-1234925618 | https://api.github.com/repos/simonw/datasette/issues/1798 | 1234925618 | IC_kwDOBm6k_c5Jm3gy | 9599 | 2022-09-02T00:01:00Z | 2022-09-02T00:01:00Z | OWNER | There's a thread about this here, but it doesn't have any workaround that look to me like they would be worth applying: https://stackoverflow.com/questions/36463531/pyyaml-automatically-converting-certain-keys-to-boolean-values | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1359557737 |