issue_comments: 491543785
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/462#issuecomment-491543785 | https://api.github.com/repos/simonw/datasette/issues/462 | 491543785 | MDEyOklzc3VlQ29tbWVudDQ5MTU0Mzc4NQ== | 9599 | 2019-05-11T21:05:54Z | 2019-05-11T21:05:54Z | OWNER | So I think `datasette inspect fixtures.db other.db` should output something like this: ```json { "fixtures": { "hash": "894870db97229e9e18b40921dc32b581da813465d672445e96e040ab2adbd229", "file": "fixtures.db", "size": 225280, "tables": { "facetable": { "count": 34, } } } ``` It currently writes it out to a file called `inspect-data.json`. Should I keep that as the default behaviour or switch it to outputting to stdout instead? Here's the current `datasette inspect --help`: ```$ datasette inspect --help Usage: datasette inspect [OPTIONS] [FILES]... Options: --inspect-file TEXT --load-extension PATH Path to a SQLite extension to load --help Show this message and exit.``` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 443023308 |