If you don't appreciate this, you're not a passionate dev!

I define my API once. 

Then I can create as many implementations as I want. maybe for testing, different bis cases whatever. And throughout I always have type safety that is not only data types/schema but ALSO API SCHEMA!!!!

Yes the API Schema you declared to be your API YES!

using effect-ts new platform package that integrated the community http api package

If you don't appreciate this, you're not a passionate dev!

I define my API once. 

Then I can create as many implementations as I want. maybe for testing, different bis cases whatever. And throughout I always have type safety that is not only data types/schema but ALSO API SCHEMA!!!!

Yes the API Schema you declared to be your API YES!

using effect-ts new platform package that integrated the community http api package

https://github.com/Effect-TS/effect/tree/main/packages/platform

cc @downshift you really want to use Effect for your API's and I'll make sure I tell you until you do lol

unless you don't code in Typescript, then fairgame. 

PS: https://github.com/SamuelLHuber/airstack-moxie-api-effect-http has a sample of this too that's public

Developer 🤓 build, develop and operate Farcaster solutions @ dtech.vision also love tech, decentralization, fitness and oldschool rap 😎

did I mention you also get Type Errors if you missed implementing some handlers? 

and yes the return types are also validated, so if you implement a handler and it has the wrong return type -> doesn't compile.

If it compiles it runs - effect-ts