type-fest VS graphql-utils

Related: https://github.com/sindresorhus/type-fest/blob/main/source/o...

Typescript doesn’t natively provide an Opaque type that we can use to define a string that has already been localized. If the data looks like a string, Typescript will consider it a string. We can however use utility types that simulate opaque types, like the Opaque definition in type-fest:

With these powerful features, you can create dynamic and expressive types. One last thing I want to mention before moving on, is that you can install libraries with which you can add more types to your project like type-fest or utility-types. These libraries contain a lot of useful types that you can use in your project.

Also, it’s not as restrictive as mutability tools — if you know what you are doing and want to ignore this limitation for a particular case, you can apply the -readonly modifier or the Writeable type from type-fest or ts-essentials.

Remember you can derive one type from another type so you can make sure they don't diverge. SetOptional type util

Some folks have built whole SQL databases and DSL compilers in the TS type system. These tend to be toy projects with disclaimers not to use them. But the type system being Turing complete[0] (for better or worse), pretty much whatever you can imagine. This project[1] is one I actually return to frequently for practical ideas.

0: https://github.com/microsoft/TypeScript/issues/14833

1: https://github.com/sindresorhus/type-fest

Have a look at SetRequired and SetOptional in type-fest

Try the Exact method provided by Type Fest, looks like it does what you're looking for

This is a fairly common scenario and available via libraries like type-fest or implementable with a couple lines of code.

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.