graphql-utils VS tsyringe

This is what I meant you should be doing anyway. Dataloader or simple field resolvers are extremely inefficient. You can use a library I created - GraphQL-Utils - to retrieve a mapping of the fields you need to JOIN and then do so with your ORM or data mapping technology of choice (Prisma, Knex.js, etc.)

By the way, I see you're using Docusaurus, something that might be kind of cool to integrate is a live GraphQL playground with some mock data if you want to spruce it up. I have a documentation for my own library, GraphQL-Utils that does this. Might be worth checking out the source code for my Sandbox component!

If you would like to see how I've gone about implementing it so far, I opened a new branch, keymap, in the GraphQL-Utils GitHub repository and if you happen to have any input on those problems I mentioned I'd really appreciate it!

I released a library, GraphQL-Utils, which contains helpers such as resolveSelections(), as well as a full NestJS integration that ships with decorators like @Selections(), which you can see above. It supports wildcards to retrieve fields that contain subselections, flat fields, deep fields, and many more options!

GitHub - Jenyus-Org/graphql-utils: Utilities and helpers to make working with GraphQL.js based APIs simpler.

I come from C# and Java so the structure just makes so much more sense and the tooling is way better. I also love the GraphQL integration and made a library to optimize queries, so yeah, I'm stuck in the ecosystem.

Check out my blog post on GraphQL-Utils if you use NestJS for GraphQL projects!

NestJS is amazing. I've been spending a lot of time with it and using its GraphQL integration to build hybrid APIs. I like it so much that I spent some time figuring out how to optimize query relations and wrote a package to aid in doing so called GraphQL-Utils.

Alguns frameworks trabalham desta forma por padrão, como é o caso do Angular, quando este não é o padrão do framework que utilizamos podemos usar alguma biblioteca, como a Inversify ou tsyringe da Microsoft.

We are writing a backend application that handles a data stream and provides REST and GraphQL endpoints to query and manage these data. We are using TypeScript with Express.js and TSyringe for our DI container.

This is exciting but also make be a bit nervous as my projects make extensive use of https://github.com/microsoft/tsyringe and the decorator changes are not going to play nice.

tsyringe

If you don’t want to tie yourself to a full web framework like Nest, there are a few DI-only frameworks that work with decorators, like TypeDI, TSyringe, or Typed Inject.

In next post I will show you how to using with other DI package like awilix , tsyringe, etc...

It is written in Typescript, it is modeled similarly to the Microsoft tsyringe (which I was using previously).

For existing projects, or if you don't want the weight of an opinionated framework like Nest, libraries like TypeDI and TSyringe can help.

I personally still always opt for that pattern to start with and refactoring to some sort of Reader monad as the application grows. Others may prefer instead to go the route of decorators and reflection with tsyringe.