-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still Alive ? #1538
Comments
I'm actively using it and also created multiple PR's, never got an answer on any of them. So I don't think so :( |
Yeah, and I'd be interested in the maintenance of only one part of the packages, not all of them. So, if others think similarly, taking over the maintenance of all of the repo would be a difficult decision. Scott |
@smolinari what parts are you interested in? |
@TriPSs - I've worked a little and am still using the Typegoose bit. Scott |
@smolinari I do have a fork of this package here that already has some fixes and i'm planning to fix more in it. It's not yet published some where (I published to private repo), will check if I can make some time soon to publish it somewhere, than maybe the development can continue there. |
@TriPSs I've also made a PR about a month and a half ago. Let me know when it's published publicly ;) |
@GP4cK it currently is :) I do have to note that I created a breaking change, still need to document this, but the change is that if the item is not found is used to return null and that now throws an error. See this commit for the change. |
I mean the npm packages. Have you published them? I couldn't find them just now... |
@TriPSs can you list your bug have been fixed |
@meodemsao Issues/PR's that are merged/released:
More fixes are always welcome ❤️ |
Latest version ? .v0.30.0 - 2021-09-30 Is active lib? This lib really helps in development, let's not let this project die, please.... |
@daniloras - Did you read this thread? @TriPSs is upkeeping a fork. See here: #1538 (comment) Scott |
It's a bit sad that @doug-martin seemed to be treating this project with care and attention then suddenly completely disappeared. I know it's OS, requires time, etc., but some guidance for the future or designating new maintainers would be nice |
I honestly find it hard to understand how some of these packages have taken so much work and then they just get abandoned... At least handing over the reigns so others can take over would be nice. I guess you can always fork but doesn't add to the usability |
Github really doesn't make it easy to hand over the reigns on personal repos. @doug-martin has done incredible work putting this project together, I'm sure he'd keep it up if he could. Really difficult to have to shoulder responsibility for the project when things change and it's no longer a top priority, and there's no way to set up another admin. |
@doug-martin thanks for the great project. if you want to leave, can you transfer this project to someone? |
It looks like @doug-martin has completely stopped working on code, at least code stored at Github, since July. I'd suggest looking at @TriPSs 's fork and supporting his work going forward. https://github.com/tripss/nestjs-query Scott |
After seeing over the years what a frequent contributor he has been to the OpenSource community I am concerned for @doug-martin; hope all is well with him. |
thank you @TriPSs this is a real saviour :) |
`@nestjs-query/*` is no longer maintained, see doug-martin/nestjs-query#1538 for more info
All is in the title.
The text was updated successfully, but these errors were encountered: