Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Migration to Typegoose #237

Open
mateja176 opened this issue Oct 12, 2019 · 2 comments
Open

Migration to Typegoose #237

mateja176 opened this issue Oct 12, 2019 · 2 comments

Comments

@mateja176
Copy link

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?

@mateja176
Copy link
Author

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).

@GrayStrider
Copy link
Contributor

GrayStrider commented Oct 21, 2019

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants