Skip to content

refactor: consider typia and nestia #23

Description

@getlarge

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions