cv VS io-ts

I'm working on a new version of my CV (v1: https://cv.git-pull.com)

This time I'm writing it in React, Angular, and Vue (TypeScript across the board). It's in the very early stages, but keep it at https://github.com/tony/cv

While doing it, I've tried to find various ways to share the chart and data code across all 3 versions. The library I found to make it happen with data akita: https://datorama.github.io/akita/

For UX it's not so easy. The truth is, some of the best UI libraries are framework specific. This creates a lot of fragmentation in the frontend community IMO. For instance react has nivo, vicious, and react-vis, but at the end of the day it's svg and canvas underneath the hood. Still though, the efforts are amazing. It makes you wonder what it'd be like if there would be just one agreed upon way to write a widget. (There's web components, custom elements... but those won't even work with typescript out of the box)

In the past few years, that stuff that's been going on with webpack v5's persistent caching, TypeScript (and its tooling), and all 3 of these frameworks getting better is amazing.

Examples of charting software I've tried: https://cv-react-v2.git-pull.com/dev/branch/v2-billboard.js/, https://cv-react-v2.git-pull.com/dev/branch/v2-plotly/, https://cv-react-v2.git-pull.com/dev/branch/v2-carboncharts/

For the first time I've found a UI suite called Carbon: https://www.carbondesignsystem.com/, an IBM thing. I'm most impressed by their chart offering. Even though it's relatively new, they maintain bindings for react, vue and angular.

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.