Future of the library

[hakimio]

@zMotivat0r do you plan to maintain this library? Is it worth starting new integrations (ie mikro-orm, firestore, sequelize, mongoose)? Do you have some plan what you'd like to do with the library?

[rewiko]

I am tempted to fork it and merge all the fixes that everyone is waiting on, but it would be better to be able to help to develop this library on this repo.

Can I become a contributor?

https://twitter.com/rewiko/status/1399790684031406080

[Jtosbornex]

I kind of thought this would eventually go into the Nestjs organization. Im interested in the future of this package as well.

[hakimio]

@Jtosbornex Since @zMotivat0r just recently joined "Trilon" (the company behind NestJS) and there is a lot of interest in the library from the community, I think it's quite possible of it becoming part of official NestJS organization.

[mcelearr]

@hakimio Really hope so. This is a great library!

[michaelyali]

Hi guys!
Thanks a lot for raising this issue and I would definitely love to have you guys (or some of you who may be really interested) as maintainers of this library. I really appreciate this and hope with your help we won't let this lib just die. Due to some really complex family conditions, I can't afford to spend as much time on it as I did in the past, but I don't want to completely bury this lib.
So, yeah @rewiko your propositions came out with just perfect timing.

[michaelyali]

Going forward, I've raised some amount of money via open collective and hadn't spend anything, so I definitely would love to share those with new maintainers as well

[hakimio]

@zMotivat0r what do you think about the idea of making this library part of NestJS organization (if @kamilmysliwiec accepts)?

[michaelyali]

@hakimio we had a conversation about it (a couple of times tbh) and a strong argument against adding it to NestJs (and I totally agree with it) is that this lib is not totally following community convention on how to provide this kinda functionality. I.e. I build it to use @Crud decorator and pass all the params there in the first place, but another and perhaps the best way to do it to use mixins. So maybe when we have mixins, plus CrudModule with forRoot with global config instead of what we have now, plus CrudModule with forFeature for controllers auto-generation or just a per-module configuration, then we could make another proposal to @kamilmysliwiec :)

[rewiko]

Thanks @zMotivat0r for getting back to us, hope your family is ok and your problems are going to be resolved.

Happy to spend some time to at least create a new release with all the bug fixes waiting to be merged.

[michaelyali]

@rewiko added you as a maintainer

[hakimio]

@zMotivat0r mixin idea theoretically seems really good, but in practice there seems to be some issues implementing it. If those could be solved, I would love to use mixin approach as well.

OT: right now all the ORM (type-orm, mikro-orm, mongoose, etc) integrations have to be added to this repository since some "core" logic is not accessible otherwise. What do you think about splitting integration core code and the integration itself into separate packages, so that people could maintain their integrations in 3rd party repositories independent from the core library?

[hakimio]

BTW, it might make sense to make @Diluka collaborator of this repository since he contributed a lot of code already.

[rogyvoje]

This is a great NestJS library and it would be wonderful to see it at least maintained. I would be happy to help out. I use it on some production projects and it is really super helpful!

[tarekbazine]

@zMotivat0r I would be happy to contribute.

Maybe we could start by creating a package roadmap in Github Projects.