Apollo Integration
See original GitHub issueHello,
I used to use Prisma alot with Apollo, and I’d like to completely replace Prisma with Cruddl, but I have a few questions:
- Is there a typeDefs generation for Cruddl as Prisma does (https://www.prisma.io/docs/prisma-cli-and-configuration/cli-command-reference/prisma-generate-xcv2/)
The reason for asking this is because currently (as far as the docs go), I’d have to setup a GraphQL server (Yoga or Apollo) with Cruddl from a GraphQL schema thats written by the developer, then another graphql server has to be made with custom resolvers, and rewrite the typeDefs (too much repetition) to get it all working the way prisma operates now.
Using the schema file as the typeDefs for Apollo server results in missing directives errors
Is there any way to shorten this process? i.e. Ability to overwrite resolvers in the schema generated by Cruddl as I’m aware that Apollo has addResolveFunctionsToSchema({ schema, resolvers })
however there is no API to access the data directly i.e. with Prisma you could do something like:
users: (parent, args, ctx, info) => ctx.db.users(args, info)
- Seeding (already answered on: https://github.com/AEB-labs/cruddl/issues/89)
Forgive me if the issue is straight forward, I’ve spent a few days playing around, researching, reading through the docs but this issue isn’t referenced anywhere
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (1 by maintainers)
A demo application (with authentication, custom resolvers) etc. would be awesome for beginners to show / explain the features and limitations of Cruddl, hoping on this with the v1 release.
I think I have a similar situation in our setup. A good portion of our schema will be handled by cruddl. However, some things still need to be handled manually. This is especially true if not all of your graphql API is serviced by Arango. In our case, a portion of the API is a proxy for REST calls, while some serve other functional needs (testing, health check, etc.). My thinking right now is that some combination of schema stitching (merge-graphql, etc.) and/or federation techniques might get me there.