beubo VS io-ts

I'm working on https://github.com/uberswe/beubo - It's a CMS similar to Wordpress but written in Go. It's still very early and it has a lot of bugs but what will make it powerful is plugins and themes. Performance is the biggest difference between Wordpress, plugins will most likely use RPC/gRPC which means they could be written in any language.

I'm mostly writing it for use with my own projects like https://tournify.io but it would be awesome if a few others found it useful too. It's a nice way for me to practice my Go programming skills.

A CMS written in Go. It’s still very early and it has the basics of user creation, multiple domain support, themes and user management by default. What will make it really powerful is plugins.

Plugins are still being developed and currently use the go plugin package which is really good for performance but can be bad for security and compatibility with versions and operating systems. I plan to either move over to using RPC instead or supporting both options.

Everything is available on GitHub under the MIT License.

https://github.com/uberswe/beubo

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.

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.

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/

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.

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.

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.

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.

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.