Skip to content
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

Open
samchon opened this issue Dec 23, 2022 · 4 comments
Open

[Discussion] who is using typia in production? #447

samchon opened this issue Dec 23, 2022 · 4 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested

Comments

@samchon
Copy link
Owner

samchon commented Dec 23, 2022

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.

@samchon samchon added documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested labels Dec 23, 2022
@samchon samchon pinned this issue Dec 23, 2022
@samchon samchon unpinned this issue Apr 30, 2023
@samchon samchon closed this as completed Apr 30, 2023
@samchon samchon reopened this Aug 23, 2023
@samchon samchon pinned this issue Aug 23, 2023
@jmroon
Copy link

jmroon commented Oct 3, 2023

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
Copy link

bogeeee commented Mar 10, 2024

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
Copy link
Contributor

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
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants