Summary: Through the datasette-graphql endpoint, JSON columns that are respected by json_columns in a local install of datasette are interpreted as plain strings in a vercel-published or fly-published instance.
I have the following fragment in my metadata.json (I only have one database and table):
If I run in a local install using datasette ., the graphql instance shows JSON as JSON.
If I publish using datasette-publish-vercel --install datasette-graphql, the JSON is interpreted as strings by the graphql endpoint. Same thing happens when I publish to fly.io.
Summary: Through the datasette-graphql endpoint, JSON columns that are respected by json_columns in a local install of datasette are interpreted as plain strings in a vercel-published or fly-published instance.
I have the following fragment in my metadata.json (I only have one database and table):
If I run in a local install using
datasette .
, the graphql instance shows JSON as JSON.If I publish using
datasette-publish-vercel --install datasette-graphql
, the JSON is interpreted as strings by the graphql endpoint. Same thing happens when I publish to fly.io.