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

-o flag is ignored #90

Open
terion-name opened this issue Mar 21, 2018 · 2 comments
Open

-o flag is ignored #90

terion-name opened this issue Mar 21, 2018 · 2 comments

Comments

@terion-name
Copy link

$ node_modules/.bin/graphql prepare -p test-dosvit-app-prisma-local -o src/experiments -g graphcool-ts --bindings --save
✔ Bindings for project database written to src/generated/prisma.ts
@kbrandwijk
Copy link
Contributor

Did you already have existing settings in your .graphqlconfig file?

@terion-name
Copy link
Author

@kbrandwijk .graphqlconfig contents:

projects:
  app:
    schemaPath: "src/schema.graphql"
    includes: ["queries/{booking,queries}.graphql"]
    extensions:
      endpoints:
        default: "http://localhost:4000"
  database:
    schemaPath: "src/generated/prisma.graphql"
    includes: ["database/seed.graphql"]
    extensions:
      prisma: database/prisma.yml
      prepare-binding:
        output: src/generated/prisma.ts
        generator: prisma-ts

But here I run cli manually for a different src and different output, set explicitly in arguments, they should have higher priority over config. Moreover, src and output are described only for one of the projects, described in config, and in cli call I don't reference it. If the config is used, than what is the logic, why it takes second project's configuration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants