-
Notifications
You must be signed in to change notification settings - Fork 467
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
Apollo CLI v3 #2611
Apollo CLI v3 #2611
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
🦋 Changeset detectedLatest commit: 3c9f806 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@trevor-scheer what are the alternatives for codegen with swift? Afaik graphql-code-generator doesn't support that use case. |
@danilobuerger we're releasing brand new Swift based codegen functionality shortly, with Apollo iOS 1.0. |
Is this still being worked on ? |
@PowerKiKi unfortunately it is not. I know this project is not in a good state, but I don't believe Apollo intends to prioritize any additional work on this repo. At this point, if you absolutely still need functionality from this repository (which isn't offered by |
WIP PR for CLI v3 (and majors for other related packages as well).
The primary purpose of these versions is to get these packages on to current versions of node and graphql. I don't intend to be adding any features, this is mostly for project health and compatibility. Particularly the lack of graphql 16 support is a specific pain point for users which I intend to address.
Please read! This project is probably no longer interesting to you. We fully intend to sunset it once we have a viable replacement in place for each of the features.
graphql-code-generator
. It's proven to be a superior tool to the codegen offering here. We use it ourselves at Apollo and have had a great experience with it. If codegen is the only reason you're using theapollo
CLI, consider this the kick you needed to abandon this tool!rover
CLI is the successor to this project. @EverlastingBugstopper and others have put a lot of love into that tool and it shows. Please use it instead! I am aware there may be command(s) which haven't made it over there yet, and for that reason this CLI continues to exist.apollo-env
. If thefetch
y bits are interesting to you for some reason, it will be helpful for me to hear about that on this PR. The rest is (was?) just node polyfills which shouldn't be applicable anymore.TODO:
*Make sure changelog entries note which project(s) has been affected. See older entries for examples on what this looks like.