Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

json_columns not respected by datasette-graphql after publishing #70

Open
mhalle opened this issue Jan 6, 2021 · 1 comment
Open

json_columns not respected by datasette-graphql after publishing #70

mhalle opened this issue Jan 6, 2021 · 1 comment
Labels
question Further information is requested

Comments

@mhalle
Copy link

mhalle commented Jan 6, 2021

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):

{
    "plugins": {
        "datasette-graphql": {
            "json_columns": [
                "dcc", "keywords", "dcc_code"
            ]
        }
}

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.

@mhalle mhalle changed the title json_columns not respected after publishing json_columns not respected by datasette-graphql after publishing Jan 11, 2021
@simonw
Copy link
Owner

simonw commented Feb 15, 2021

Did you pass the metadata.json file to the publish command, like this?

datasette publish vercel data.db -m metadata.json --install datasette-graphql

@simonw simonw added the question Further information is requested label Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants