still maintained?

[katylava]

Is this package still being maintained? We'd like to use the latest version of django-filter but can't, since graphene-django-extras requires an older version. Also the current version requires an alpha version of graphene-django, which breaks stuff for us.

Is there a good alternative for graphene-django-extras?

[paulsermon-gemfair]

I'm going to say that it looks like a nearly dead project. I think it needs more contributors. I may need to transition my schema away from this package completely next year, or start contributing myself.

[washeck]

@eamigo86 could you please comment on the maintenance status of this library? I need compatibility with Django 4.0 and I can invest some capacity to get #181 to a good shape to be merged but I need to know if there is chance to merge it or I should rather start my fork.

Thank you

[eamigo86]

Hi there, sorry for the delay in responding, but in recent months I have been a father and the truth is that it takes up a lot of the little free time I had. However, I'm planning to start working on a new version with more features off the box, and compatible with Django >=3.2.
I'll most likely start working in the new version in mid-January 2023.

[washeck]

@eamigo86 Thanks for the reply, I fully understand that.

Anyway, if you had just a few minutes to donate to this project, I prepared #191 which updates the supported versions to Django 4.0 & 4.1, removes the already EOLed versions and cleans up the tox/Github Actions setup so the tests passes on all supported versions.

It should be pretty easy to review.

[shanx]

Nice @eamigo86 congrats on becoming a father! And I totally understand that experience, as I have had it too :)

Maybe it would be nice to open up the repo to more maintainers? Or transfer the repo to https://github.com/jazzband so maintaining it could be a community effort. Thanks for all of your work 🙏