You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI shouldn't merge/use by default config or there should be an opt out flag to not use config by default.
Only "dirty fix" that works for getting fresh schema and then use vscode plugin by defining localSchemaFile in config, is, to remove apollo.config before running service:download.
make use apollo service:download --endpoint="..." my-schema.json to not use apollo.config.js if present by default.
Actual outcome:
if apollo.config.js is present, it's gonna be used for cli commands and cannot be overriden.
This causes various issues:
if localSchemaFile is used within config file, it will throw error (file doesn't exists)
unable to fetch fresh schema ( used for validation/compilation of types on CI. UI and API are 2 separated projects )
How to reproduce the issue:
Versions apollo@2.6.0
The text was updated successfully, but these errors were encountered:
Hotell
changed the title
[cli]: apollo service:download uses always uses apollo.config.js if present
[cli]: apollo service:download always uses apollo.config.js if present
Mar 12, 2019
Hi @Hotell! Sorry this has taken so long to look at. I think this is a problem with our documentation around configuring projects. Right now, the apollo config isn't meant to be used with more than one project. If you're using a monorepo with multiple projects under a single root, you'd need to use separate apollo.config.js files for each of those projects at their respective roots.
If I'm misunderstanding, please provide a simple reproduction repo and steps to show what's going wrong for you, and I can reopen
Intended outcome:
Only "dirty fix" that works for getting fresh schema and then use vscode plugin by defining
localSchemaFile
in config, is, to remove apollo.config before runningservice:download
.apollo service:download --endpoint="..." my-schema.json
to not useapollo.config.js
if present by default.Actual outcome:
if
apollo.config.js
is present, it's gonna be used forcli
commands and cannot be overriden.This causes various issues:
localSchemaFile
is used within config file, it will throw error (file doesn't exists)How to reproduce the issue:
Versions
apollo@2.6.0
The text was updated successfully, but these errors were encountered: