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

refactor: consider typia and nestia #23

Open
getlarge opened this issue Feb 1, 2024 · 1 comment
Open

refactor: consider typia and nestia #23

getlarge opened this issue Feb 1, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@getlarge
Copy link
Owner

getlarge commented Feb 1, 2024

They both seem great candidates to :

  • replace class-validator and class-transformer to declare DTOs used for validation
  • replace nests-swagger the same interface created for Typia can also be inferred to generate API properties and response can be generated by Nestia TypedRoute

This results in classes containing fewer decorators and more performant validation steps.

I already successfully tested Nestia integration in this app.

References

@getlarge getlarge added the enhancement New feature or request label Feb 1, 2024
@getlarge
Copy link
Owner Author

getlarge commented Feb 6, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant