-
Notifications
You must be signed in to change notification settings - Fork 339
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 maintained? #462
Comments
Hi, I'm afraid we can say indeed that this project is mostly unmaintained :/ I'm very sad about this situation. |
@ziirish My company are using I didn't realize there was a lack of maintainers because it's always worked so well for us! |
@ziirish same here. |
I can also help ... as much as I can. |
@ziirish Thanks for the reply, this was my fear also as I noticed no activity :-( Is there an alternative project that people are now using for building a REST server in python? I thought this was the most popular library to use? If there is something newer/better that people are moving to then thats the natural order of things, but otherwise I'd love to help keep this project alive. |
I'm also interested in contributing to the project. |
It might be of interest. |
@carlosvega None of that helps with the triage and merging of the 43 open pull requests, unfortunately |
Hi, Thanks for your answers and interest in flask-restx! I will take some time in the coming days/weeks to invite some of you to take responsibilities in the project and I will also try to prepare a new release with urgent compatibility fixes (I definitely won't have time to review new features). This should allow me to document the process and see if our current material is still up-to-date. |
@ziirish That sounds like a great plan. We definitely want to keep all of your previous hard work in this project going. |
Hello @ziirish & ty for your efforts. |
Just looking at previously merged PRs and it seems there was a coverage integration that auto ran, and example of this is on this PR: #327 Maybe reenabling this would give greater confidence when merging some of the outstanding PRs. Also whilst we wait for @ziirish we could start reviewing other's PRs to make sure they are ready to be merged. |
@ziirish happy to help too. |
Happy to help too, my company is using flask-restx for a small project. It would save us time to be able to keep it instead of rebuilding our API. Happy to help if I can. |
Hi, I created restx-monkey to patch most of the painful problems. I personally use it in my work place on production servers. I hope it will helps you. Feedback is welcome :) |
Thanks Ryu-CZ that helps, but in the medium to long term we might need to fork this project (...again) |
Man, this project was perfect for me. I just finished onboarding my whole API to it and came to report what I thought was a bug, only to see that this :( maintainers, if you don't have time anymore can you please take the necessary steps to onboard some of the many people who volunteered to take over? |
That sounds like it's just the werkzeug compatibility fix. But the problem of nobody merging PRs etc remains. |
It makes me really happy to hear that! |
While I can't say that I could become a maintainer for the whole project, I'd love to at least add |
Just for completeness, I posted over on the other thread (#503 (comment)) and I'm going to try and find a bit of time to maintain this project going forwards. At least keeping up compatibility with any new Flask releases as a start. |
Going to suggest we move this discussion over to #510 😄 |
Looks like great progress on this, thanks everyone, will now close this issue. |
Ask a question
There are several pull requests and issues that have not been replied to by anyone that contributes to this project for sometime.
Is there a specific process or person(s) that need to be contacted so outstanding feature requests are dealt with?
Thanks in advance.
The text was updated successfully, but these errors were encountered: