home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 405026800

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/294#issuecomment-405026800 https://api.github.com/repos/simonw/datasette/issues/294 405026800 MDEyOklzc3VlQ29tbWVudDQwNTAyNjgwMA== 45057 2018-07-14T14:24:31Z 2018-07-14T14:24:31Z CONTRIBUTOR

I had a quick look at this in relation to #343 and I feel like it might be worth modelling the inspected table metadata internally as an object rather than a dict. (We'd still have to serialise it back to JSON.)

There are a few places where we rely on the structure of this metadata dict for various reasons, including in templates (and potentially also in user templates). It would be nice to have a reasonably well defined API for accessing metadata internally so that it's clearer what we're breaking.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
327365110  
Powered by Datasette · Queries took 0.919ms · About: github-to-sqlite