sliproad
io-ts
sliproad | io-ts | |
---|---|---|
3 | 80 | |
9 | 6,602 | |
- | - | |
0.0 | 4.9 | |
almost 3 years ago | 5 months ago | |
Go | TypeScript | |
GNU General Public License v3.0 only | 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.
sliproad
-
Spacedrive – A File Explorer from the Future
I tried something similar with a project of mine[1], with a focus on API rather than frontend so I could build tailored apps for each device/user. At some point I should get around to finishing it -- I mostly focused on S3 and local filesystem compatibility, but being able to explore filesystems from other devices (maybe through an agent) is a neat idea.
[1] https://github.com/gmemstr/sliproad
- Show HN: Sliproad 2.1 – Merge Filesystems Together
-
Ask HN: What Are You Working On?
Rewriting my storage application from Go to Rust, since it offers some better ergonomics for what I want it to do - Ideally I want to merge a bunch of different file and object storage providers together into one API/web interface: https://github.com/gmemstr/sliproad/tree/3.0-rust-rewrite
Also working on reading more books :)
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?
spacedrive - Spacedrive is an open source cross-platform file explorer, powered by a virtual distributed filesystem written in Rust.
zod - TypeScript-first schema validation with static type inference
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)
runtypes - Runtime validation for static types
fp-ts - Functional programming in TypeScript
joi - The most powerful data validation library for JS [Moved to: https://github.com/hapijs/joi]
newtype-ts - Implementation of newtypes in TypeScript
typebox - Json Schema Type Builder with Static Type Resolution for TypeScript
Yup - Dead simple Object schema validation
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
class-transformer - Decorator-based transformation, serialization, and deserialization between objects and classes.