Arguments order issue? about graphql-faker HOT 6 CLOSED

@peteruithoven Thanks for reporting 👍
Looking into it right now 🔎 🐞

from graphql-faker.

@peteruithoven I just published 1.7.4 which cleanups Yargs code.

graphql-faker --extend http://localhost:8091/graphql --forward-headers Authorition ./temp.faker.graphql

Should be:

graphql-faker --extend http://localhost:8091/graphql --forward-headers Authorition -- ./temp.faker.graphql

Note: -- after --forward-headers Authorition it's required since forward-headers accepts space separated list of header names so without -- Yargs thinks that ./temp.faker.graphql is another header.

from graphql-faker.

Thanks for looking into this so quickly! This totally fixes my npm script challange.
We can now simply add a script like:

  "scripts": {
    "start-faker": "graphql-faker --extend http://localhost:8091/graphql --forward-headers Authorization --"
  }

And call it with something like: npm run start-faker -- faker.graphql

from graphql-faker.

I though pointing to the relevant Yargs docs would be a bit to technical?

from graphql-faker.

@peteruithoven If you switch places --extend and --forward-headers you can omit -- both in package.json and npm call.

from graphql-faker.

Good point. I'll try including that in #50

from graphql-faker.