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
part of my model is class-based ( because it need to be decorated for the object-relational mapping and should have a default constructor ) and
although I would be able to declare additional interfaces, this would lead to duplicating all the property definitions of the classes to the corresponding interfaces.
Do you have any plan to support a class-based model?
The text was updated successfully, but these errors were encountered:
I think this should be possible and fairly simple to implement, with the understanding that only class properties would be looked at, not methods.
There's also the slightly more complicated matter of constructor variables, e.g. constructor(public value: string). I would expect that to also be included in the model.
I'll look into this and see if it can be done without introducing unnecessary complexity.
@gms1 I've opened up a pull request to support this behavior: #14
Since you opened this issue, please take a look at those changes and provide some feedback. I've added a suite of tests for these changes and done some manual testing, but I'd like your input.
part of my model is class-based ( because it need to be decorated for the object-relational mapping and should have a default constructor ) and
although I would be able to declare additional interfaces, this would lead to duplicating all the property definitions of the classes to the corresponding interfaces.
Do you have any plan to support a class-based model?
The text was updated successfully, but these errors were encountered: