Robin Baum

Hey @piotrmoszkowicz, thanks for reporting.

Hey @kartsims, you could use the respositoryMode for that. This mode lets you re-use your models. See https://github.com/RobinBuschmann/sequelize-typescript#how-to-enable-repository-mode for details.

Hey @kangzj , `save` and `update` should still work on your instances (`instance.save();`) So the created objects are still active records. Otherwise you have to do it like you said:...

Hey @MagicLegend, sry for the late reply. Unfortunately I won't have time in the near future to investigate this any further. But what I can say from now is, that...

Hey @BjarkeNL, I think the issue is indeed caused by [this](https://github.com/sequelize/sequelize/issues/10579#issuecomment-486027564) behaviour of babel. I've got the impression that `_defineProperty` overrides the previously defined getters and setters created by sequelize....

@loganfsmyth thanks for giving more insights. So `babel-plugin-proposal-class-properties` is doing it the right way 🤔 @Telokis @BjarkeNL For now I can only provide a workaround (Overriding the defined properties again):...

@DalerAkhmetov Good point. One need to add the association keys as well like so: ```ts [ ...Object.keys(new.target.rawAttributes), ...Object.keys(new.target.associations), ].forEach(propertyKey => { // .. }); ``` (Untested, but) Hope this helps...

Hey @sonacy, thanks for bringing this up. Unfortunately this isn't supported yet.

@karimabdelhakim yeah, this would be useful and should be implemented. For now you can achieve this like so: ```ts @Column({ ..., validate: { isDate: {msg: 'your message'} } }) ```...

Hey @gintsgints, I don't really get your point here. Can you explain it a little bit further?