Make human_description_en explicitly available to output renderers
Open
Nobody has claimed this yet.
plugins
small
- Dominant language
- Python
- Stars
- 11.5k
- Forks
- 904
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 18
Description
datasette-atom uses this:
if data.get("human_description_en"):
title += ": " + data["human_description_en"]
It's a nice way to generate a useful title for a filtered table.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with datasette_atom/init.py at the referenced lines to understand how the renderer consumes human_description_en, then trace how output renderer data is assembled in Datasette. Done means output renderers can explicitly access human_description_en for filtered-table titles, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100