ogen
zod
ogen | zod | |
---|---|---|
10 | 292 | |
1,106 | 30,778 | |
7.0% | - | |
9.5 | 9.1 | |
7 days ago | 6 days ago | |
Go | 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.
ogen
-
I write HTTP services in Go after 13 years (Mat Ryer, 2024)
https://github.com/ogen-go/ogen
Write openapi definition, it'll do routing, definition of structs, validation of JSON schemas, etc.
All I need to do is implement the service.
Validating an integer range for a querystring parameter is just too boring. And too easy to mistype when writing it manually.
Anyways, so far only been playing, so haven't found the bad parts yet.
-
Create Production-Ready SDKs with Goa
Ogen
-
How to OpenAPI?
But also this project https://github.com/ogen-go/ogen It worth keeping an eye on.
-
Go stack for REST APIs?
https://github.com/ogen-go/ogen/ is my potential replacement, need to evaluate it fully though.
-
Ideas on how to make certain package public on a private repository
One package I have my eyes on is ogen: https://github.com/ogen-go/ogen
- ogen: spec-first OpenAPI v3 codegen for Go
-
Any good OpenAPI 3.x spec generator for a Go REST API?
We have used https://github.com/deepmap/oapi-codegen in production for a long time and it's rock solid. Up and coming https://github.com/ogen-go/ogen is being developed rapidly and also worth keeping an eye on.
-
Generate RESTful CRUD with Ent and ogen
This post introduces a new OSS project that we are announcing today, ogent. ogent is a bridge between Ents capability to create OpenAPI v3 documents and ogen, an OpenAPI v3 Code Generator for Go.
-
chai - a library for type safe http handlers via generics with automatic swagger generation
There is ogen for OpenAPI v3 code generation.
zod
-
Simplifying Form Validation with Zod and React Hook Form
[Zod Documentation](https://zod.dev/) [Zod Error Handling](https://zod.dev/ERROR_HANDLING?id=error-handling-in-zod) [React-Hook-Form Documentation](https://react-hook-form.com/get-started) [Hookform Resolvers](https://www.npmjs.com/package/@hookform/resolvers)
-
Figma's Journey to TypeScript
This is a very fair comment, and you seem open to understanding why types are useful.
"problems that are due to typing" is a very difficult thing to unpack because types can mean _so_ many things.
Static types are absolutely useless (and, really, a net negative) if you're not using them well.
Types don't help if you don't spend the time modeling with the type system. You can use the type system to your advantage to prevent invalid states from being represented _at all_.
As an example, consider a music player that keeps track of the current song and the current position in the song.
If you model this naively you might do something like: https://gist.github.com/shepherdjerred/d0f57c99bfd69cf9eada4...
In the example above you _are_ using types. It might not be obvious that some of these issues can be solved with stronger types, that is, you might say that "You rarely see problems that are due to typing".
Here's an example where the type system can give you a lot more safety: https://gist.github.com/shepherdjerred/0976bc9d86f0a19a75757...
You'll notice that this kind of safety is pretty limited. If you're going to write a music app, you'll probably need API calls, local storage, URL routes, etc.
TypeScript's typechecking ends at the "boundaries" of the type system, e.g. it cannot automatically typecheck your fetch or localStorage calls return the correct types. If you're casting, you're bypassing the type systems and making it worthless. Runtime type checking libraries like Zod [0] can take care of this for you and are able to typecheck at the boundaries of your app so that the type system can work _extremely_ well.
[0]: https://zod.dev/ note: I mentioned Zod because I like it. There are _many_ similar libraries.
-
From Flaky to Flawless: Angular API Response Management with Zod
Zod is an open-source schema declaration and validation library that emphasizes TypeScript. It can refer to any data type, from simple to complex. Zod eliminates duplicative type declarations by inferring static TypeScript types and allows easy composition of complex data structures from simpler ones. It has no dependencies, is compatible with Node.js and modern browsers, and has a concise, chainable interface. Zod is lightweight (8kb when zipped), immutable, with methods returning new instances. It encourages parsing over validation and is not limited to TypeScript but works well with JavaScript as well.
- TypeScript Essentials: Distinguishing Types with Branding
-
You can’t run away from runtime errors using TypeScript
Zod is a TypeScript-first schema declaration and validation library. It helps create schemas for any data type and is very developer-friendly. Zod has the functional approach of "parse, don't validate." It supports coercion in all primitive types.
-
Best Next.js Libraries and Tools in 2024
Link: https://zod.dev/
-
Popular Libraries For Building Type-safe Web Application APIs
You can check out their documentation here.
-
Epic Next JS 14 Tutorial Part 4: How To Handle Login And Authentication in Next.js
You can learn more about Zod on their website here.
-
What even is a JSON number?
In JS, it's a good idea anyway to use some JSON parsing library instead of JSON.parse.
With Zod, you can use z.bigint() parser. If you take the "parse any JSON" snippet https://zod.dev/?id=json-type and change z.number() to z.bigint(), it should do what you are looking for.
-
Error handling in our form component for the NextAuth CredentialsProvider
We will validate our input using client-side zod. Zod handles TypeScript-first schema validation with static type inference. This means that it will not only validate your fields, it will also set types on validated fields.
What are some alternatives?
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
class-validator - Decorator-based property validation for classes.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
joi - The most powerful data validation library for JS [Moved to: https://github.com/sideway/joi]
rest - Web services with OpenAPI and JSON Schema done quick in Go
typebox - Json Schema Type Builder with Static Type Resolution for TypeScript
swag - Automatically generate RESTful API documentation with Swagger 2.0 for Go.
Yup - Dead simple Object schema validation
kin-openapi - OpenAPI 3.0 (and Swagger v2) implementation for Go (parsing, converting, validation, and more)
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
kiota - OpenAPI based HTTP Client code generator
io-ts - Runtime type system for IO decoding/encoding