"config" section in metadata.json (root, database and table level)

[simonw]

Split off from #274

Metadata should an optional "config" section at root, table or database level.

The TableView and RowView and DatabaseView and BaseView classes could all have a .config("key") method which knows how to resolve the hierarchy of configs.

This will allow individual tables (or databases) to set their own config settings for things like sql_time_limit_ms

[simonw]

So the lookup priority order should be:

• table level in metadata
• database level in metadata
• root level in metadata
• --config options passed to datasette serve
• DATASETTE_X environment variables

[simonw]

It feels slightly weird continuing to call it metadata.json as it starts to grow support for config options (which already started with the units and facets keys) but I can live with that.

[simonw]

This is obsoleted by the work happening here:

• Proposal: Combine settings, metadata, static, etc. into a single datasette.yaml File #2093