Apollo-tooling: [vscode-apollo] Changing service in `apollo.config.js` requires a full VSCode restart

Created on 7 Feb 2019  路  3Comments  路  Source: apollographql/apollo-tooling

If you change the service name in apollo.config.js (and the corresponding API key in in .env), VSCode will report errors until you quit and re-open. It appears as though the schema is being fetched for the original service; I see this in an error message but don't want to paste a screenshot here because it's sensitive.

Most helpful comment

@JakeDawkins Please reopen, the extension still does not reflect localSchemaFile change until VSCode restart.

Tested in current version 2.21.0.

See the original report https://github.com/apollographql/apollo-tooling/issues/669#issuecomment-484400735 by @kazinad.

All 3 comments

This should be fixed with #897 馃帀

Thank you @JakeDawkins !

@JakeDawkins Please reopen, the extension still does not reflect localSchemaFile change until VSCode restart.

Tested in current version 2.21.0.

See the original report https://github.com/apollographql/apollo-tooling/issues/669#issuecomment-484400735 by @kazinad.

Was this page helpful?
0 / 5 - 0 ratings