-
-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] who is using typia
in production?
#447
Comments
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. |
Hey samchon, 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 |
I used typia in production for a couple of products. |
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. |
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.
The text was updated successfully, but these errors were encountered: