-
Notifications
You must be signed in to change notification settings - Fork 6
README should mention package is deprecated #31
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
Comments
My comment in #22 was a bit misleading, so I removed it. The name "gql-next" has nothing to do with GraphQL-core-next (as GraphQL-core v3 was called earlier). It was rather a very interesting, type-safe, alternative approach for creating a Python GraphQL client, very different from the original gql implementation. The name "gql-next" was chosen because it was meant to eventually/potentially replace gql. However, since then no further work happened in this project, while gql was actively maintained and further developed and is now based on GraphQL-core 3. This project should be considered more like an experiment and an invitation to continue development and experimentation in this direction. I agree this should be reflected in the README and the name and title should be changed. It's not good to have two projects with the exact same title. But I would want to leave this to the creator of this project @ekampf. |
I agree! |
@ekampf I was particulary interested by the ability to generate the types via the cli. I can't figure out another client providing this feature for python. Do you have a suggestion ? |
According to #22 gql-next is deprecated in favor of gql v3. The readme should also mention that to avoid confusion.
The text was updated successfully, but these errors were encountered: