typegraphql-prisma
io-ts
typegraphql-prisma | io-ts | |
---|---|---|
6 | 80 | |
861 | 6,611 | |
- | - | |
6.8 | 4.9 | |
3 months ago | 5 months ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
typegraphql-prisma
-
TypeGraphQL/Nexus vs GraphQL Codegen TypeScript resolvers
I like nexus with prisma better. I feel like typegraphql shines the most when using with orms like MikroORM of TypeORM. Though prisma with typegraphql is not a bad idea, there's a cool plugin that can generate crud resolvers.
- TypeORM and go-to ORM's 2021. TypeORM dead?
-
One ORM to rule them all
I think Prisma is not only modern ORM. If we want to build a GraphQL api, it will help us boost our work. We don't have to waste our time to make CRUD operations, we just define Prisma model and it will do it for us: https://github.com/MichalLytek/typegraphql-prisma/blob/main/Readme.md
-
TypeORM: Connection vs getConnection, EntityManager vs getManager, Repository vs getRepository
Prisma works well with TypeGraphQL. In fact, there's a generator that makes it easier to generate TypeGraphQL types and CRUD resolvers from your Prisma 2 schema: https://github.com/MichalLytek/typegraphql-prisma
-
How the F**** does anyone use Prisma in production?
There are also several tools that allow you generate a GraphQL CRUD API based on Prisma, such as Amplication, KeystoneJS or typegraphql-prisma.
-
Building a GraphQL CRUD API for your Database with TypeGraphQL & Prisma
Learn more about other advanced operations you can apply to your GraphQL resolvers, such as custom resolvers, authorization, middleware and additional decorators to your Prisma schema and models here.
io-ts
-
TDD
Qué rico. Si tenés chance meté un proceso de code review fuerte, y para el tema de I/O probá a usar https://github.com/Effect-TS/schema ó https://github.com/gcanti/io-ts que les da una solución obvia al tema de "tipos para lo que devuelva el backend", aunque es en realidad mucho más capaz que eso.
-
Domain modelling with State Machines and TypeScript by Carlton Upperdine
My fave is still io-ts (https://github.com/gcanti/io-ts/blob/master/docs/index.md) as I find it more flexible than zod at the ingress. The author is also working on the Effect ecosystem which also looks interesting.
-
Why I Like Using Maps (and WeakMaps) for Handling DOM Nodes
I’ve been using io-ts for this and been very happy with it. [1] It’s similar to Swift’s Coding protocol in case you’re familiar.
[1] https://gcanti.github.io/io-ts/
-
Can someone recommend a library for data parsing similar to Zod, but with better support for input transformations/preprocessing?
Yeah, there are a few new concepts and it's not the easiest to pick up right away. The best introduction is here on the main documentation page.
- libraries you are happy that you discovered them
- Is React for small projects an Overkill?
-
how to strictly type this?
We use https://github.com/gcanti/io-ts/blob/master/Decoder.md which has a very similar interface. It can even be used to mutate the data using https://github.com/gcanti/io-ts/blob/master/Decoder.md#the-parse-combinator.
-
Typescript advanced bits: function overloading, never and unknown types
A good way to significantly improve the reliability of your app is via improving type-safety by moving away from using any to unknown. One relevant example could be when you type your backend responses and when stringifying JSON to using unknown combined with some sort of runtime type checking. It can be done either by using built-in functionality like type guards or using an external library like io-ts, zod or yup.
-
I found 10,000x faster TypeScript validator library
Usage of TypeBox is similar with io-ts and zod, but it is much powerful and faster than them. Also, TypeBox can generate JSON schema very easily. Therefore, if you're looking for a validator library for new project and not suffering from legacy codes, I think TypeBox would be much better choice than io-ts and zod. TypeBox can totally replace them.
-
Validate your data with Zod
This check can be done with different libraries like: io-ts, typebox, or zod. These libraries allow you to create objects that represent your typescript definitions. Then, these objects can be used at runtime to validate the received data, in addition, you can also convert this object to a Typescript definition to have all the benefits of using typescript. These objects can be called schema validations because they are responsible for the data validation.
What are some alternatives?
mikro-orm-graphql-example - A MikroORM (v4) example project for GraphQL made with Typescript using TypeGraphQL
zod - TypeScript-first schema validation with static type inference
nexus-plugin-prisma - Deprecated
class-validator - Decorator-based property validation for classes.
runtypes - Runtime validation for static types
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
fp-ts - Functional programming in TypeScript
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
joi - The most powerful data validation library for JS [Moved to: https://github.com/hapijs/joi]