graphql-utils VS ts-toolbelt

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.

There are a bunch of awesome type utility libraries that may boost your works on types, like ts-toolbelt, utility-types, SimplyTyped, etc., which you can already use.

We have only scratched the surface of type manipulation in Typescript, if you want to get your mind blown, checkout community projects like ts-toolbelt and type-challenges.

Do you mean https://github.com/millsp/ts-toolbelt? You didn’t provide a link so I’m not sure which repo you’re referring to.

I am guessing that since it does not exists as an built in type, in utility-types, or in ts-toolbelt that it currently isn't possible.

Since posting this, some comments have made me aware that ts-toolbelt has this feature and a couple other really useful ones built in. So their source code could be worth skimming through to see how they did things.

I was curios enough to dug the definition along with a related types Narrowable and Cast

ts-toolbelt has a "Path" Type https://github.com/millsp/ts-toolbelt