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/sqlite-utils/issues/517#issuecomment-1344965367 | https://api.github.com/repos/simonw/sqlite-utils/issues/517 | 1344965367 | IC_kwDOCGYnMM5QKor3 | 9599 | 2022-12-10T01:26:31Z | 2022-12-10T01:26:31Z | OWNER | At some point I should drop it from all of these other projects too: https://cs.github.com/?scopeName=All+repos&scope=&q=user%3Asimonw+%223.6%22+path%3A.github%2Fworkflows%2F* | {
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1487757143 | |
| https://github.com/simonw/datasette/issues/1942#issuecomment-1344959032 | https://api.github.com/repos/simonw/datasette/issues/1942 | 1344959032 | IC_kwDOBm6k_c5QKnI4 | 9599 | 2022-12-10T01:11:26Z | 2022-12-10T01:11:26Z | OWNER | One way this could work: if plugins request it, a block like this is added to the page: ```html <script type="application/json+datasette" id="datasette-json"> { "...": "..." } </script> ``` Then a function could be provided which extracts and parses that data: ```javascript var data = await datasette.jsonData(); ``` Why an `await`? Because then I could have it work the exact same way if the data is NOT available on the page - it could trigger a `fetch()` call for the same stuff. So loading it on the page becomes an optional performance optimization. | {
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1487738738 |