I(@Kononnable ) am not planning to add any more features to typeorm-model-generator. Some minor changes proposed in PRs might get merged, but any complex feature will get rejected. I'll try to check issues/PRs from time to time, but truth be told this project isn't currently my main priority.
I think typeorm-model-generator is in a pretty good state, there are some quirks and bugs, but it's mostly easy to go around them. Basic features(common features for this kind of software) are there, if anyone needs more complex ones they can easily implement them on their own(in a non generic way, customized to theirs build environment - USECASES).
I don't think typeorm should be considered as option for new projects other than prof of concepts or some workshop exercises. Typeorm is in a bad place. It's been like that for few years and I don't believe this will change any time soon(if ever). There are even some long standing bugs which can result in data loss. Some of the fixes are blocked by inability to introduce breaking changes - next branch(planned 0.3.0 version) has been with us for 3 years now and yet there are no concrete plans on releasing it or throwing that code away.
I've decided to mark this project as maintenance only to make sure that any newcomers think twice before choosing typeorm for their ORM.
vuki656, denodaeus, mzavaletavargas, Surdok, dss-barreto and 40 morev1d3rm3, fuszenecker, MattSPalmer, king-ppap, simwai and 1 moreeklenin and Stanback
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4