ts-protoc-gen
schemats
Our great sponsors
| ts-protoc-gen | schemats | |
|---|---|---|
| 2 | 2 | |
| 1,325 | 1,024 | |
| 0.5% | 0.0% | |
| 2.9 | 0.0 | |
| 3 months ago | over 2 years ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | 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.
ts-protoc-gen
- Creating type definition from protocol buffer
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::note When using remote APIs, we often have the possibility to generate the types automatically from a JSON schema for REST APIs, from protobuf files for gRPC-based APIs, from a database schema, etc. You might even be using an external API through an SDK that already provides you with all types. In such cases, the creation of specialized Error classes is not mandatory. However, it might still be a good idea to do so to provide application-specific errors rather than bubbling up 3rd-party low-level errors. For such cases, the upcoming Ecma TC39 proposal for Error Cause is useful as it allows to chain errors. Polyfills exist: Pony Cause or error-cause. :::
schemats
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::note When using remote APIs, we often have the possibility to generate the types automatically from a JSON schema for REST APIs, from protobuf files for gRPC-based APIs, from a database schema, etc. You might even be using an external API through an SDK that already provides you with all types. In such cases, the creation of specialized Error classes is not mandatory. However, it might still be a good idea to do so to provide application-specific errors rather than bubbling up 3rd-party low-level errors. For such cases, the upcoming Ecma TC39 proposal for Error Cause is useful as it allows to chain errors. Polyfills exist: Pony Cause or error-cause. :::
-
Preferred SQL ORM
Using a library such as that one https://github.com/SweetIQ/schemats
What are some alternatives?
protobuf-ts - Protobuf and RPC for TypeScript
crystal - 🔮 Graphile's Crystal Monorepo; home to Grafast, PostGraphile, pg-introspection, pg-sql2 and much more!
graphql-error-handling-with-union-and-fpts
knex-types - Generate TypeScript definitions (types) from a PostgreSQL database schema.
effect - A fully-fledged functional effect system for TypeScript with a rich standard library
deno-nessie - A modular Deno library for PostgreSQL, MySQL, MariaDB and SQLite migrations
graphql-yoga - 🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.
fp-ts - Functional programming in TypeScript
Stack - Tech Stack developed by The Guild
sql-lint - An SQL linter
pony-cause - Ponyfill and helpers for the standardized Error Causes