Is this project going to be maintained in the long term?

[dzcpy]

No description provided.

[jinpy666]

Also, I'm curious to know that a long-term maintenance project is needed.

[helmsonsen]

as long as there is no better maintained and supported fork,
we, at getitdone.rocks, currently don't have any plans to drop support from our end

[dzcpy]

Also, I'm curious to know that a long-term maintenance project is needed.

If interested maybe we can do some work together? Seems like we share similar tech stack and from the same country

[dzcpy]

as long as there is no better maintained and supported fork, we, at getitdone.rocks, currently don't have any plans to drop support from our end

Thanks for your effort!

[afilp]

We would like to use mongoose instead of typeorm.

Is it possible that mongoose can be supported in this fork too?
(there were some PRs on the original repo back then)

Thanks a lot.

[zaro]

@afilp there is no plan to do that for now. If you want to take these old PRs and submit them here I will take a look.

[afilp]

@zaro Is there a way to not use the (somehow deprecated) "class-validator" and be able to use yup/zod/zoi instead?
It seems that we can only do validations with the "class-validator" through the CRUD.

[zaro]

@afilp I am not sure if it's possible to swap it for another validator lib. The package uses the default builtin validator of nestjs : https://docs.nestjs.com/techniques/validation#using-the-built-in-validationpipe .

Maybe support for other validator libraries can be added, but I am not sure how ATM.

[afilp]

@zaro It would be very useful to add such support, not sure who could overtake this though (I do not have the knowledge). I am afraid that this whole solution is unmaintained for too long for our projects to be sustainable. Thanks.