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
I open separate workspaces in vscode for project-1 and project-2 instead of pointing to the repo's root.
From what I see in the docs, the extension will not work if apollo.config.js isn't present in the workspace repo (frontend-project-1 or frontend-project-2), but I don't want to duplicate the config files in all the subfolders.
Is there any way I can provide a custom path for the config file for each subproject I import in my workspace?
I currently work with a multi-folder monorepo with a dedicated folder for all the configs.
I open separate workspaces in vscode for project-1 and project-2 instead of pointing to the repo's root.
From what I see in the docs, the extension will not work if
apollo.config.js
isn't present in the workspace repo (frontend-project-1
orfrontend-project-2
), but I don't want to duplicate the config files in all the subfolders.Is there any way I can provide a custom path for the config file for each subproject I import in my workspace?
┆Issue is synchronized with this Jira Task by Unito
┆Link To Issue: https://apollographql.atlassian.net/browse/NEBULA-1867
The text was updated successfully, but these errors were encountered: