issue_comments: 636908972
This data as json
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/790#issuecomment-636908972 | https://api.github.com/repos/simonw/datasette/issues/790 | 636908972 | MDEyOklzc3VlQ29tbWVudDYzNjkwODk3Mg== | 9599 | 2020-06-01T15:01:00Z | 2020-06-01T15:01:00Z | OWNER | Setting messages just needs access to the response. Reading messages needs access to both request AND response, since it needs to clear the messages that are being displayed. That's if the messages are persisted exclusively in cookies - which makes sense for Django since it's designed to run as many different load-balanced processes. Since Datasette is a single process which can access an on-file database, maybe consider storing the flash messages within Datasette memory itself - a sort of session mechanism? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 628499086 |