-
Notifications
You must be signed in to change notification settings - Fork 1
Expose data model as GraphQL API #1
Comments
Actually, the article above requires recreating all the type definitions manually, which violates DRY. TypeGraphQL only requires decorating existing classes which seems like a much better approach https://github.com/19majkel94/type-graphql |
Thanks, I want to experiment with that a bit tomorrow 😄 |
I added a GraphQL layer to the application. Now |
I'll work on a lib that auto-generates basic resolvers (list, get by id, create, update and delete) for |
Looks great so far Caio thanks! And yeah an auto-generated CRUD would be 💃 There are a few read-only entity methods that already exist, e.g. https://github.com/infojunkie/quizzical/blob/master/src/entity/Enrollment.ts#L44 - we would want to expose these to the client. So it would be good to be able to annotate these methods to become fields in the auto-generated entity type or query. |
Another option here found on HN today: https://github.com/acro5piano/typed-graphqlify |
Picking up where this left off with TypeGraphQL + Apollo Server |
E.g. as per https://medium.com/@govorov/creating-graphql-api-with-koa-and-typeorm-8ec0ce2eaadc
The text was updated successfully, but these errors were encountered: