issue_comments

Documentation: https://github.com/dogsheep/dogsheep-beta/blob/0.4/README.md#custom-results-display

Needs documentation.

I'm pleased with how this works now.

Challenge: the dogsheep-beta.yml configuration file that is passed to the dogsheep-beta index command needs to also be made available to Datasette itself, so that it can read the configuration.

Let's say it can either be duplicated in the plugins configuration block of the metadata.yml OR you can do this in metadata.yml:

yaml plugins: dogsheep-beta: config_file: dogsheep-beta.yml

If this turns out to be too inefficient I could add a display text column to the search_index table which is designed to be populated with arbitrary JSON by the indexing query, which can then be used to render the template fragment.

If this performs well enough (100 displayed items will be 100 extra display_sql calls) then I'll go with this as the design for the feature.

display_sql could be optional. If it's not defined, a row object is passed to the template which is the row that's stored in search_index. If display_sql IS defined then it's executed and the result is made available as a display object in addition to the row object.

Maybe I can take advantage of https://sqlite.org/np1queryprob.html here - I could define a SQL query for fetching the "display" version of each item, and include a Jinja template fragment in the configuration as well. Maybe something like this: yaml photos.db: photos_with_apple_metadata: sql: |- select sha256 as key, 'Photo in ' || coalesce(place_city, 'unknown') as title, ( select group_concat(normalized_string, ' ') from labels where labels.uuid = photos_with_apple_metadata.uuid ) as search_1, date as timestamp, 1 as category from photos_with_apple_metadata display_sql: |- select sha256, place_city, date from photos_with_apple_metadata where sha256 = :key display: |- <img src="https://photos.simonwillison.net/i/{{ display.sha256 }}.jpeg?w=600"> <p>Taken in {{ display.place_city }} on {{ display.date }}</p>