-
Notifications
You must be signed in to change notification settings - Fork 765
Serializer mutation choice field creation fails with django-rest-framework 3.15.0 #1507
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
Comments
Seems like there is already a pull request for this: #1506. Should've checked those first 😄 |
@MrThearMan #1506 has been merged. Please check if that fixes the issue. Feel free to reopen the issue if that's not the case. |
Thanks, works like a charm! A patch release for this would be much appreciated! |
@kiendang Would you be able to release a v3.2.1 with this fix to PyPI? |
Pinging @firaskafri. When you have time could you look at making a patch release v3.2.1? Thanks! |
@kiendang @firaskafri Any updates on the PyPI? |
What is the current behavior?
See title. This is due to an
isinstance
check inconverters.get_choices
that changes the iterable if the choices are an OrderedDict. Django REST Framework 3.15.0 changed from OrderedDicts to regular dicts, so this check no longer converts the iterable, meaning the loop now tries to iterate the dict by keys, but unpack it to two variables, which is not possible.I've created an example repo reproducing the issue: https://github.com/MrThearMan/graphene-django-bug. The repo contains the exact traceback for the error.
What is the expected behavior?
I should be able to use serializer mutations with choice fields in DRF 3.15.0.
Changing the
isinstance
check toisinstance(choices, dict)
should solve the issue without any breaking anything for older versions of DRF, as OrderedDicts are subclasses of dicts.The text was updated successfully, but these errors were encountered: