-
Notifications
You must be signed in to change notification settings - Fork 862
ArangoDB Connector #1645
Comments
ArangoDB is cool |
Hi folks, Alan from ArangoDB here. If there's anything we can do to help you with the connector feel free to ping me. |
I could use this connector. Any progress or any tips if I want to take a shot at it myself? |
@joelgetaction I don't think I've heard from anyone working on one and we don't have one listed at https://www.arangodb.com/arangodb-drivers/ at the moment, so give it a shot if you want. If you need assistance on the ArangoDB side of things you can hang around in our community slack: https://www.arangodb.com/community/ -- there's a |
Yeah, I could really use this connector as well. |
This would be really cool! Any docs on how to write connectors/drivers? |
Has anyone started working on it? |
I found this, today, during a search for prisma + arangodb --> https://github.com/AEB-labs/cruddl At my most recent project, we like the way it plugs in to Apollo and/or Yoga, so that we can continue to benefit from all the nice things we get between yoga & apollo-client (like subscriptions 😄 ) . |
@armenr would you be able to share how you implemented subscriptions with cruddl please? |
Unfortunately Cruddl doesn't support subscriptions just yet, however it is in active development. |
any developments in this? |
@itsezc - Any progress on the subscriptions front? What would be the easiest way to find out? |
The last we heard for Cruddl about Subscriptions is AEB-labs/cruddl#16 However afaik they will likely be added, I'm getting really impatient with waiting on Prisma so I've gone full on Cruddl and I'm really interested in making a PR for subscription support, if there doesn't seem to be any progress on it. |
AEB-labs/cruddl is not really ideal because it forces you to write and control ArangoDB from GraphQL SDL, not the other way around. So it's not really a solution here! We need a proper Prisma connector. |
This feature requests serves as a central place to discuss development and progress for the ArangoDB connector.
The text was updated successfully, but these errors were encountered: