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.

Sign up for GitHub

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

Jump to bottom

[vscode-apollo] Changing service in apollo.config.js requires a full VSCode restart #987

Open
justinanastos opened this issue Feb 7, 2019 · 3 comments
Open

[vscode-apollo] Changing service in apollo.config.js requires a full VSCode restart #987

justinanastos opened this issue Feb 7, 2019 · 3 comments
Labels
🗒️ component - vscode related to editor tooling

Comments

@justinanastos
Copy link
Contributor

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.
@JakeDawkins
Copy link
Contributor

This should be fixed with #897 🎉

@justinanastos
Copy link
Contributor Author

Thank you @JakeDawkins !

@iki
Copy link

iki commented Nov 19, 2019 •
edited
Loading

@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 #669 (comment) by @kazinad.

@JakeDawkins JakeDawkins reopened this Nov 19, 2019
@abernix abernix added the 🗒️ component - vscode related to editor tooling label Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🗒️ component - vscode related to editor tooling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@iki @abernix @justinanastos @JakeDawkins