-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comparison with https://github.com/zino-app/graphql-flutter #12
Comments
@Sewdn the main addition seems to be the addition of an sql normalized cache (a51909d and 09ecb32). You can take a look at the old diffs, though they're a bit misleading (there are a lot of apparent additions that are from prior work, not sure why). Meanwhile, I've cleaned up most of the outstanding commits to |
@micimize Thanks a lot for the explanation and extra background. We know where to look now. And we'll probably shift focus to |
@Sewdn while what @micimize said is somewhat true, this fork is not limited to the SQL feature, and so far I have tried to replicate the same behaviour as apollo graphql. this was a fork of the graphql-flutter library at a time the development was stale. I have applications that depend on this repo and I will continue to support it. If you are looking for a more mature community of developers for a graphql library, please you could use graphql-flutter library. This library is aimed at achieving one purpose an apollo alternative for flutter and it wouldn't have been possible without the amazing work done in the graphql-flutter repo. I wasn't comfortable with the process of the maintenance of the parent library a while back which affected my project, so I am determined to get this repo working fully. Again graphql-flutter library is now more active than before and you can obviously contribute there. This library is not a competition with graphql-flutter library at least for now, and graphql-flutter is a great library |
Hi, this package was originally a fork of https://github.com/zino-app/graphql-flutter: https://github.com/juicycleff/flutter-graphql
Then it transferred to another namespace (snowballdigital) and it lost its reference as a fork of zino-app.
Could you please describe how this package differs from the original package that is still being maintained and what design decisions made you decide to go a different direction (and not try to steer to a single effort, maintained and contributed by more devs?)
We as a team are also willing to contribute, but must decide first what package is the most promising to end up as the project with most traction and community support.
Thanks!
The text was updated successfully, but these errors were encountered: