You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
I won't go over all of typegoose's selling points here (feel free to do so yourself) however the biggest benefit it offers is the ability to not have to duplicate your type definitions for typescript and mongoose (by writing classes or interfaces and schema definitions respectively). In a nutshell, through usage of decorators typegoose generates mongoose schemas for us.
The upgrade is simple with the most noticeable difference lying in src/models/User.ts as can be seen in the following diff (other file changes are mostly unrelated).
Given that #218 seems to be popular, I don't think this is gonna fly for the same reasons. The project seems to position itself as a "starter", not as "boilerplate". In latter case I agree, the suggestion would make perfect sense.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I won't go over all of typegoose's selling points here (feel free to do so yourself) however the biggest benefit it offers is the ability to not have to duplicate your type definitions for typescript and mongoose (by writing classes or interfaces and schema definitions respectively). In a nutshell, through usage of decorators typegoose generates mongoose schemas for us.
Taking the above into consideration, who is in favor of updating TypeScript-Node-Starter to use typegoose?
The text was updated successfully, but these errors were encountered: