-
Notifications
You must be signed in to change notification settings - Fork 731
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
Investigate how to distribute CLI outside of SPM #2562
Comments
I think the only reasonable way to do this is by checking the Package.resolved file. We should bundle the CLI version in the There are 3 ways to get Apollo:
CLI InstallationThe I think that maybe an SPM plugin command just for actually building and installing the CLI might be a good compromise. It works with both Xcode and Package.swift projects very easily, and doesn't require The documentation for installation of the Codegen CLI will need to be updated for this. The plugin command can just run the |
I think we should rather:
This way it's clear to the user what versions were used and they have access to all the tools (binary + repo) to fix any mismatched version problems. Trying to guess paths, etc. is opportunity for things not to work as expected. I'd rather put the power back into the hands of the user. |
Using the CLI through SPM plugins is not the best experience and requires the use of options such as
--disable-sandbox
in order to unlock the full functionality. Is there a way we can distribute the CLI outside of SPM and maintain a strong link to the correct version of apollo-ios.The text was updated successfully, but these errors were encountered: