Redesign default .json format

The default JSON just isn’t right. I find myself using ?_shape=array for almost everything I build against the API.

[simonw]

Great point about CORS, I hadn’t considered that.

I think I’m going to keep the Link: header (added in #1014) because I quite enjoy using it with GitHub and WordPress, but I’m not going to have it be the default way of doing pagination. For the default shape I’m now leaning towards this:

{
  "total": 36,
  "rows": [{"id": 1, "name": "Cleo"}],
  "next_url": "https://latest-with-plugins.datasette.io/fixtures/facetable.json?_next=5"
}

So three keys: total, rows and next_url. Then extra keys can be added using ?_extra= with various named bundles.

[simonw]

OK, I’m back to the “top level object as the default” side of things now - it’s pretty much unanimous at this point, and it’s certainly true that it’s not a decision you’ll even regret.