dug VS io-ts

Just joined the sub after coming across it dozens of times while learning things to help my homelab. My first post is a shameless plug for a CLI tool I made that quickly helps users get an idea of how much their DNS has propagated. I use it all the time for my self hosted stuff (recently when i was playing with external-dns) and wanted to share to see if it can help anyone else. https://dug.unfrl.com https://github.com/unfrl/dug

For people who want to understand, learn about, or stay on top of their, DNS check out dug. Its a cli tool I made to help visualize DNS propagation but is a great learning tool.

https://github.com/unfrl/dug

https://dug.unfrl.com

Good article, totally correct that that is how to definitely 100% get the correct answer.

The bottom of the article, with 'other ways' got me thinking that another way to get what is very probably the correct answer is asking a bunch of other DNS servers what they think the correct answer is.

Using dug (https://github.com/unfrl/dug) like: dug -q NS jvns.ca

Gotta post this every time theres a big DNS issue, which seems daily now.

Check out Dug! Its a global DNS propagation/monitoring toolon the CLI: https://github.com/unfrl/dug/

This release is primarily focused on the 'Watch' feature (-w, --watch) which allows users to monitor their DNS propagation in realtime.

https://github.com/unfrl/dug

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.