issue_comments: 564214355
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/577#issuecomment-564214355 | https://api.github.com/repos/simonw/datasette/issues/577 | 564214355 | MDEyOklzc3VlQ29tbWVudDU2NDIxNDM1NQ== | 9599 | 2019-12-10T19:47:17Z | 2019-12-10T19:47:17Z | OWNER | The reason I've been dragging my heels on adding template rendering to the Datasette class is that it feels messy - should that class be responsible for both data access AND template rendering? I think I can come to terms with this thanks to plugins. The Datasette class can represent the family of features that plugins affect - which means that having it expose the template rendering API is reasonable. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 497171390 |