New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan for getting the new JSON format query views working #2109
Comments
OK, these issues will do for the plan. |
I'm going to do this work in a fresh branch, copying bits over from here as needed: |
Here's the code I'm going to be entirely replacing: datasette/datasette/views/database.py Lines 213 to 530 in 18dd88e
Plus this weird class in datasette/datasette/views/table.py Lines 701 to 749 in 18dd88e
|
New decision: I had originally decided that the HTML view would just use data that could otherwise be extracted from the JSON view if you fed in enough extras. I've changed my mind. I'm OK with the HTML view getting a few bonus things available in its context, provided those are clearly documented for template authors. This should help avoid me having to make many changes to the templates themselves. HTML-specific stuff will be things like |
Once again I'm tempted to formalize the extra HTML context as a Here's an example of Hugging Face doing that: https://github.com/huggingface/transformers/blob/1689aea73346816b936b84932e12b774974e61a6/src/transformers/training_args.py#L622C1-L624 from dataclasses import dataclass, field
@dataclass
class TrainingArguments:
output_dir: str = field(
metadata={"help": "The output directory where the model predictions and checkpoints will be written."},
) |
I've been stuck on this for too long. I'm breaking it down into a full milestone:
https://github.com/simonw/datasette/milestone/29
The text was updated successfully, but these errors were encountered: