go-helpers
runtypes
go-helpers | runtypes | |
---|---|---|
1 | 22 | |
5 | 2,548 | |
- | 0.3% | |
5.6 | 5.6 | |
8 months ago | 3 months ago | |
Go | TypeScript | |
GNU General Public License v3.0 or later | 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.
go-helpers
-
JSON Schema bundling finally formalised
```
The "IsInteger" validator can of course be interpreted as a type, the important thing is though that it can be customized using type parameters and that we can add any number of additional validators that do advanced things (e.g. we could define an "IsPrime" validator that checks for primality of the number).
I find this more elegant than having both a "type" field and various extensions for validations that you need to remember. The validator list mechanism also makes it easy to chain validations and perform sub-validations for lists or maps. I have an open-source implementation of this written in Golang [1] that I use in all my projects. It enables me to write a form specification and a Go struct and validate as well as coerce unstructured data into the struct. It makes it very easy to validate complex, hierarchical documents like configuration files as well, is easy to extend and provides nice errors.
1: https://github.com/kiprotect/go-helpers/tree/master/forms
runtypes
-
When should I use runtime checks (and which runtime checker should I use)?
In terms of which runtime checker I should use. The first tutorial I saw suggested 'Zod', doing a bit more searchign yielded other options such as 'runtypes'.
-
An almost religious case for Rust
Runtypes would probably be a better example.
-
'The best thing we can do today to JavaScript is to retire it’ Douglas Crockford
this has been solved by several packages, runtypes https://github.com/pelotom/runtypes being my favorite
-
How to force a type when importing a JSON file?
I personally like https://github.com/pelotom/runtypes because it bundles your Schema Info and the corresponding Typescript types
- Why doesn’t TypeScript natively do any type checking
-
Create d.ts for API response
When I have to deal with data from API calls, I usually use a runtime typing library like Runtypes or Zod to check the responses at the boundary. These libraries can automatically give you TS types (using their static or infer utilities) to use throughout the rest of the project.
-
Typing for JSON Payloads
Also runtypes and (as mentioned below) zod.
-
How to check that an 'unknown' object has a specific key and that the key is a specific type?
Seconding the recommendation to use a library for this. runtypes and io-ts are two other alternatives.
-
Check types at the top level or in each function?
I wouldn't reinvent the wheel: https://github.com/pelotom/runtypes
-
Minimal and fast runtime API payload sanitiser and error message handling
What does your library provide that others don't? For example: https://github.com/colinhacks/zodhttps://github.com/hapijs/joihttps://github.com/jquense/yuphttps://github.com/gcanti/io-tshttps://github.com/pelotom/runtypeshttps://github.com/sindresorhus/ow
What are some alternatives?
myzod
zod - TypeScript-first schema validation with static type inference
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
typescript-is
schema-org-json-schemas - Generate JSON Schemas from Schema.org classes
io-ts - Runtime type system for IO decoding/encoding
type-fest - A collection of essential TypeScript types
typegraphql-prisma - Prisma generator to emit TypeGraphQL types and CRUD resolvers from your Prisma schema
typescript-json-schema - Generate json-schema from your Typescript sources
ts-auto-guard - Generate type guard functions from TypeScript interfaces