Import of .env file not working about vscode-graphql HOT 7 CLOSED

Interesting, thanks for reporting.

Can you try the .env file value without the quotes?
Like: AUTH_TOKEN_ENV=xxx

from vscode-graphql.

@divyenduz Yes, it works. Thanks. But than other packages can not handle the values. I believe with quotes is the default.

from vscode-graphql.

hi @divyenduz, it is possible to allow also values in quotes?

from vscode-graphql.

Not yet I think based on this issue. I will need to investigate that.

from vscode-graphql.

@divyenduz thanks in advance - currently it also don't work for me without quotes.

from vscode-graphql.

Can verify that this is happening.

My .graphqlconfig.yml:

projects:
  foo:
    schemaPath: schema.graphql
    includes: ["**/*.{graphq}"]
    extensions:
      endpoints:
        default:
          url: ${env:GRAPHQL_API}
          headers:
            Authorization: "Bearer ${env:GRAPHQL_TOKEN}"

graphql get-schema downloads the schema without issue. However the VSCode plugin does not seem to validate queries. When I enter the token in the yml file directly, the plugin does work.

My .env file by the way does not use quotes around both values.

I have tried:

• Converting from yaml to json
• Adding quotes or removing in .env file
• Adding quotes or removing in config file
• Removing one of env variables mentioned in the config

The only thing that works for me is not using {env:ENV_VARIABLE} at all. And just to reiterate, graphql get-schema does indeed retrieve the schema when I use {env:etc} in the config, so the settings should be correct.

Also, I'm on Mac. Perhaps the .env file can't be loaded by the plugin on Mac?

from vscode-graphql.

A fix for this is available in 0.1.8 via #98

from vscode-graphql.