effect

And if you want more power at the type level, use effect/schema https://github.com/effect-ts/effect/tree/main/packages/schem...

Any chance you could run this on the Effect codebase? Definitely an example of a project that can be hard to navigate due to its scope and gaps in documentation https://github.com/Effect-TS/effect

It isn’t typed since the response from the http call can be anything. It could be a Todo, a generic success wrapper that contains a Todo, or maybe it was recently changed to return a Checklist instead of a Todo. Since the response can be anything we have two options, either make the type be any or unknown. any is an escape hatch typescript provides that allows anything, so if you access a field that doesn’t exists on the response you’ll get a runtime exception. With unknown typescript doesn’t let you do anything with the value until you figure out the type. In this example the next step would be to try to decode that unknown into a Todo, or fail with some error[1]. This guarantees that the object your code expects is actually what you are expecting both at compile time and runtime. Given the goal of effect is to provide type safe trackin