issue_comments: 1613887492

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/2093#issuecomment-1613887492 https://api.github.com/repos/simonw/datasette/issues/2093 1613887492 IC_kwDOBm6k_c5gMfgE 9599 2023-06-29T22:40:25Z 2023-06-29T22:40:25Z OWNER

I'm strongly in favour of combining settings, configuration and plugin configuration.

I'm not keen on mixing in metadata as well - that feels like a different concept to me, and I'm unhappy with how that's already had things like plugin settings leak into it.

I'm not yet sold on TOML - I actually find it less intuitive than YAML, surprisingly. They all have their warts I guess.

Datasette already has the ability to consume JSON or YAML for metadata - maybe it could grow TOML support too? That way users could have a datasette.json or datasette.yaml or datasette.toml file depending on their preference.

In terms of metadata: since that's means to be driven by a plugin hook anyway, maybe one of the potential sources of metadata is a metadata nested object in that datasette.* configuration file. Or you can have it in a separate metadata.json or bundled into the SQLite database or some other plugin-driven mechanism.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 1781530343