ticketing
ticketing copied to clipboard
refactor: consider `typia` and `nestia`
They both seem great candidates to :
- replace
class-validatorandclass-transformerto declare DTOs used for validation - replace
nests-swaggerthe same interface created for Typia can also be inferred to generate API properties and response can be generated by NestiaTypedRoute
This results in classes containing fewer decorators and more performant validation steps.
I already successfully tested Nestia integration in this app.
References
One potential blocker: Nestia does not provide decorators for TypedMessagePattern and TypedEventPattern; an issue has already been created.
I might consider creating custom decorators following recipes for TypedRoute => TypedBody