issue_comments: 1109174715

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/1720#issuecomment-1109174715 https://api.github.com/repos/simonw/datasette/issues/1720 1109174715 IC_kwDOBm6k_c5CHKm7 9599 2022-04-26T00:40:13Z 2022-04-26T00:43:33Z OWNER

Some of the things I'd like to use ?_extra= for, that may or not make sense as plugins:

  • Performance breakdown information, maybe including explain output for a query/table
  • Information about the tables that were consulted in a query - imagine pulling in additional table metadata
  • Statistical aggregates against the full set of results. This may well be a Datasette core feature at some point in the future, but being able to provide it early as a plugin would be really cool.
  • For tables, what are the other tables they can join against?
  • Suggested facets
  • Facet results themselves
  • New custom facets I haven't thought of - though the register_facet_classes hook covers that already
  • Table schema
  • Table metadata
  • Analytics - how many times has this table been queried? Would be a plugin thing
  • For geospatial data, how about a GeoJSON polygon that represents the bounding box for all returned results? Effectively this is an extra aggregation.

Looking at https://github-to-sqlite.dogsheep.net/github/commits.json?_labels=on&_shape=objects for inspiration.

I think there's a separate potential mechanism in the future that lets you add custom columns to a table. This would affect .csv and the HTML presentation too, which makes it a different concept from the ?_extra= hook that affects the JSON export (and the context that is fed to the HTML templates).

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