-
Notifications
You must be signed in to change notification settings - Fork 22
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
Version 2.00+ Doesn't work with service and .js config file. #239
Comments
That should definitely cause a better error message :/ Do you get any popups? Generally, the extension supports either a So either of these would be valid configurations: module.exports = {
client: {
service: {
name: "datocms-test",
url: "<env>",
headers: { authorization: "Bearer <env>" },
},
includes: ["./queries/**/*.gql"],
},
}; or module.exports = {
client: {
service: {
name: "datocms-test",
localSchemaFile: "./schema.graphql",
},
includes: ["./queries/**/*.gql"],
},
}; Could you try those to see if they work for you? |
this is what I tried:
|
Did it work? |
@phryneas no :) same error. if i have the same config on 1.20 it works. |
Hmm... just as part of the elimination process, does it work if you inline the And if that doesn't work, does it work as a Just trying to find out which step breaks for you here :) |
@phryneas tried both, pasting in the actual keys so no process.env. and i tried with a json config file. |
Also, basic infos: what version of VSCode are you using and what's your operating system? |
If you're a windows user, could you please try the build in #240? |
My Apollo vscode extention doesn't work using newer versions.
I've created a config file looking like this: (apollo.config.js)
module.exports = { client: { localSchemaFile: "./schema.graphql", service: { name: "datocms-test", url: "<env>", headers: { authorization: "Bearer <env>", }, }, includes: [ "./queries/**/*.gql",], }, };
If i use version 2.00 + the vscode extension gives me this error:
Service stats could not be loaded. This may be because you're missing an apollo.config.js file or it is misconfigured. For more information about configuring Apollo projects, see the guide here (https://go.apollo.dev/t/config).
And if I use 1.20.0 it works without changing the config file.
The text was updated successfully, but these errors were encountered: