This repository has been archived by the owner on Jun 29, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 137
[Poll] Continuation of feature/4? #356
Labels
Comments
@hasezoey I haven't looked into the feature/4 branch but when there are some useful features inside, I would love to see these changes in master. Unfortunately, my time is very limited at the moment... |
currently but it would be a breaking change |
I think it's worth it, even it's a breaking change. |
Closed - It will be integrated in 6.0.0, but a poll about how in #373 |
hasezoey
referenced
this issue
in typegoose/typegoose
Aug 5, 2019
- outsourcing all functions in the Typegoose Class - refactoring all test-models for the new style - adding migration note for it
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
mainly targeting @Ben305 @vinczedani @szokodiakos, but feedback from anyone is appreciated
I would ask if the continuation of the branch(/ something like that) would be appreciated?
Advantages would be:
await new DummyModel({prop: 'hi'} as DummyType).save();
would not in any case require the typegoose(current) function to build a model, but still require the virtual properties ....Disadvantages would be:
would target something like
Typegoose@6.0.0
for this kind of featureThe text was updated successfully, but these errors were encountered: