[Discussion] who is using `typia` in production?

[samchon]

If you're using typia in production level, can you introduce me?

It would better if you are pasting production homepage URL with logo image.

[jmroon]

I'm planning on it!

Unfortunately it's a private enterprise app so I won't be able to share, but I'm currently on the path to migrate our existing flask backend to NestJS.

I looked at writing out class-transformers, but it's both complex for juniors to understand and our frontend schemas are already very complex. Since our frontend schemas are already defined, typia/nestia are just drop in solutions that will provide validation without any added effort. And since it all lives on the edge of the controllers, it's also a very low risk solution for us.

[bogeeee]

Hey samchon,
i'm happy to announce having switched the validators for restfuncs from typescript-rtti to Typia !
I solved it, using a 2 stage transform (which is still a bit hacky) which you can see here.

Especially i liked that Typia has a prune validator which i made the default for the lib user, so they can do cool stuff with it
Would be cool, if you list me under "Utilization cases" !

[ryoppippi]

I used typia in production for a couple of products.
It is really works well.
We have so many type definitions for API, but we didn't have solutions to convert them to actual runtime code.
Typia solved it!

[ramiroaisen]

Using typia in production at Converflow, https://converflow.com.ar. We are using typia for OpenAPI schema generation and validation of query strings, request JSON payloads, output JSON payloads, path params validation.

[samchon]

Using typia in production at Converflow, https://converflow.com.ar. We are using typia for OpenAPI schema generation and validation of query strings, request JSON payloads, output JSON payloads, path params validation.

@ramiroaisen This function would be useful for you

https://typia.io/docs/llm/application/

[Mlocik97]

I can't share much information, but in Caterpillar Digital (Cat® Central) we are about to use it in JavaScript codebase (not TypeScript, no bundler). We will feed it OpenAPI specs.

Two weeks ago we tried to implement Zod validation POC with use of ts-to-zod library in our JS codebase. It failed due to a looot of BUGs inside the package, it generated code that wasn't syntactically correct, couldn't handle circular references and so on. So week ago, I looked into typia and ajv. We got to decision to use Typia and today I've made successful POC.

I assume we will use Typia in prod in about 3 weeks.

E: update, the implementation is done, not just POC I started yesterday, but fully finished today. I guess it will go to production right next week.

Typia is amazing tool. Thank you.

E2: update, thanks to typia we discovered already around 5 BUGs and it seems we will see each day more results. It's still not even deployed, just manual testing in local env.

E3: I shouldn't have used Typia... now in my job, they want me to collect and process 200k logs generated just in 7 days in QA env, each for failed validation of upstream service. 😂😅