Ülgen Sarıkavak
Ülgen Sarıkavak
Or maybe, somehow, we can do some partial / incremental changes? I think it'd be more productive and beneficial for everyone.
Hey everyone, i used existing PR and solved all left errors: https://github.com/graphql-python/graphene-django/pull/905
Hey @jkimbo, for `DJANGO_CHOICE_FIELD_ENUM_V3_NAMING` settings, instead of defaulting it to `True` i think this setting should be removed and instead, we should intruduce a new one for `V2_NAMING` to revert...
@ganwell There is small issue with commits in my branch, i can fix it tomorrow. There is no failing test in it, so i think we can continue from there.
@ganwell All versions can be found in related PR. They were all the latest ones when the time of that PR.
@jkimbo @ganwell I couldn't catch why the things @ganwell recommended is needed. Everything was already done in #905 I'll check the test-tox config there when i have time but i...
Oh okay, i see what you recommend in that last comment @jkimbo, sorry. I think it makes sense.
@jkimbo and all the other people 🙂 What will we do with this release? It's more than two years.
@AntonOfTheWoods I started writing graphql APIs in Python with graphene-django and moved to Strawberry later. I was watching almost all of the core developers moving from graphene to strawberry, and...
@tcleonard I do 🌹