-
Notifications
You must be signed in to change notification settings - Fork 121
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
Set Ferry as a replacement for Artemis #541
Comments
cc @vasilich6107, marking you if you want to chime in on this decision! |
Makes sense) |
Hi! Thanks for reaching out. I am not familiar with all the features of Artemis. Still, from what I see it is also based on the gql-dart ecosystem with gql/gql-link/gql-exec, differences are mainly in the area of caching/fetchPolicies/normalization and code generation. I would be happy if you point your users to ferry as a replacement. I would also mention I invite users from artemis to come to discord https://discord.gg/Pu8AMajSd to discuss migration approaches. |
That's perfect, I'll do it! |
Hi, discord link does not work here nor on the ferry pub.dev |
The one in the readme (from GitHub, not on pub) should work! |
Hi guys, do we have tutorial/instructions to swap Artemis to Ferry? |
Hey guys!
I'm the owner of Ferry's "competitor", Artemis.
Both projects have been born isolated (and if I recall correctly, you've already reached me a couple of years ago talking about unification), and now it's been a long time since I've been able to work on mine's: initially I was working closely with Flutter and GraphQL, and was able to keep it running, but it's not the case anymore.
I'm here to ask if you think Ferry could be framed as a fully featured alternative to Artemis and, if so, if I can mark Artemis as archived/deprecated, forwarding users to here.
Thanks for the attention.
The text was updated successfully, but these errors were encountered: