{"html_url": "https://github.com/simonw/datasette/issues/577#issuecomment-564214355", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/577", "id": 564214355, "node_id": "MDEyOklzc3VlQ29tbWVudDU2NDIxNDM1NQ==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-12-10T19:47:17Z", "updated_at": "2019-12-10T19:47:17Z", "author_association": "OWNER", "body": "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?\r\n\r\nI 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.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 497171390, "label": "Utility mechanism for plugins to render templates"}, "performed_via_github_app": null}